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: gaf at blu.org (Jerry Feldman)
- Date: Sat, 12 Dec 2015 07:38:15 -0500
- In-reply-to: <22123.3812.983470.161719@snorkack.blazemonger.com>
- References: <20151211114214.GH27495@randomstring.org> <22123.3812.983470.161719@snorkack.blazemonger.com>
Note that /proc/meminfo contains some information regarding hugepages. On 12/11/2015 12:59 PM, Daniel Barrett wrote: > 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 > > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix PGP key id:B7F14F2F PGP Key fingerprint: D937 A424 4836 E052 2E1B 8DC6 24D7 000F B7F1 4F2F
- References:
- [Discuss] khugepaged + vmware = massive CPU load
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] khugepaged + vmware = massive CPU load
- From: dbarrett at blazemonger.com (Daniel Barrett)
- [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):