On 04/12/2010 10:21 AM, Nick Piggin wrote:
All data I provided is very real, in addition to building a ton of
packages and running emerge on /usr/portage I've been running all my
real loads. Only problem I only run it for 1 day and half, but the
load I kept it under was significant (surely a lot bigger inode/dentry
load that any hypervisor usage would ever generate).
OK, but as a solution for some kind of very specific and highly
optimized application already like RDBMS, HPC, hypervisor or JVM,
they could just be using hugepages themselves, couldn't they?
It seems more interesting as a more general speedup for applications
that can't afford such optimizations? (eg. the common case for
most people)
The problem with hugetlbfs is that you need to commit upfront to using
it, and that you need to be the admin. For virtualization, you want to
use hugepages when there is no memory pressure, but you want to use ksm,
ballooning, and swapping when there is (and then go back to large pages
when pressure is relieved, e.g. by live migration).
HPC and databases can probably live with hugetlbfs. JVM is somewhere in
the middle, they do allocate memory dynamically.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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>