BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] khugepaged + vmware = massive CPU load
- Subject: [Discuss] khugepaged + vmware = massive CPU load
- From: dbarrett at blazemonger.com (Daniel Barrett)
- Date: Fri, 11 Dec 2015 12:59:00 -0500
- References: <20151211114214.GH27495@randomstring.org>
On December 11, 2015, Dan Ritter wrote: >Normally your system keeps track of memory in 4KB pages. They're >analogous to filesystem blocks. [...] A hugepage is a 2MB page. Dan, thanks for a beautiful explanation. I really appreciate it. >In the 2.x kernel series where they were invented, hugepages had >to be turned on explicitly (there's a sysctl) and applications >had to request them. Hmm... when I upgraded from 14.04 to 15.10, this included a move from a 3.x kernel to a 4.x kernel. Perhaps transparent hugepages got enabled by default in 4.x. -- Dan Barrett dbarrett at blazemonger.com
- Follow-Ups:
- [Discuss] khugepaged + vmware = massive CPU load
- From: gaf at blu.org (Jerry Feldman)
- [Discuss] khugepaged + vmware = massive CPU load
- References:
- [Discuss] khugepaged + vmware = massive CPU load
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] khugepaged + vmware = massive CPU load
- Prev by Date: [Discuss] khugepaged + vmware = massive CPU load
- Next by Date: [Discuss] khugepaged + vmware = massive CPU load
- Previous by thread: [Discuss] khugepaged + vmware = massive CPU load
- Next by thread: [Discuss] khugepaged + vmware = massive CPU load
- Index(es):