Re: [PATCH 00 of 41] Transparent Hugepage Support #17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/06/2010 12:01 AM, Chris Mason wrote:
On Mon, Apr 05, 2010 at 01:32:21PM -0700, Linus Torvalds wrote:

On Mon, 5 Apr 2010, Pekka Enberg wrote:
AFAIK, most modern GCs split memory in young and old generation
"zones" and _copy_ surviving objects from the former to the latter if
their lifetime exceeds some threshold. The JVM keeps scanning the
smaller young generation very aggressively which causes TLB pressure
and scans the larger old generation less often.
.. my only input to this is: numbers talk, bullsh*t walks.

I'm not interested in micro-benchmarks, either. I can show infinite TLB
walk improvement in a microbenchmark.
Ok, I'll bite.  I should be able to get some database workloads with
hugepages, transparent hugepages, and without any hugepages at all.

Please run them in conjunction with Mel Gorman's memory compaction, otherwise fragmentation may prevent huge pages from being instantiated.

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]