On 04/06/2010 09:00 PM, Christoph Lameter wrote:
I don't think gcc is worst case. Workloads that benefit from large pages are
those with bloated working sets that do a lot of pointer chasing and do little
computation in between. gcc fits two out of three (just a partial score on
the first).
Once you have huge pages you will likely start to optimize for locality.
Pointer chasing is bad even with huge pages if you go between multiple
huge pages and you are beyond the number of huge tlb entries supported by
the cpu.
A hugetlb miss is serviced from the L2 or L3 cache. A smalltlb miss is
serviced from main memory. The miss rate is important, but not nearly
as important as fill latency.
--
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>