Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19

Paul Jackson
2005-11-06T18:19:42Z

Linus wrote:
> The thing is, if 99.8% of memory is cleanable, the 0.2% is still enough to
> make pretty much _every_ hugepage in the system pinned down.

Agreed.

I realized after writing this that I wasn't clear on something.

I wasn't focused the subject of this thread, adding hugetlb pages after
the system has been up a while.

I was focusing on a related subject - freeing up most of the ordinary
size pages on the dedicated application nodes between jobs on a large
system using
* a bootcpuset (for the classic Unix load) and
* dedicated nodes (for the HPC apps).

I am looking to provide the combination of:
1) specifying some hugetlb pages at system boot, plus
2) the ability to clean off most of the ordinary sized pages
from the application nodes between jobs.

Perhaps Andy or some of my HPC customers wish I was also looking
to provide:
3) the ability to add lots of hugetlb pages on the application
nodes after the system has run a while.
But if they are, then they have some more educatin' to do on me.

For now, I am sympathetic to your concerns with code and locking
complexity. Freeing up great globs of hugetlb sized contiguous chunks
of memory after a system has run a while would be hard.

We have to be careful which hard problems we decide to take on.

We can't take on too many, and we have to pick ones that will provide
a major long term advantage to Linux, over the forseeable changes in
system hardware and architecture.

Even if most of the processors that Andy has tested against would
benefit from dynamically added hugetlb pages, if we can anticipate
that this will not be a substained opportunity for Linux (and looking
at current x86 chips doesn't require much anticipating) then that
might not be the place to invest our precious core complexity dollars.

--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401