Re: [patch 18/18] hugetlb: my fixes 2

[Nishanth Aravamudan <nacc@us.ibm.com>]

On 23.04.2008 [14:11:36 -0700], Nishanth Aravamudan wrote:
> On 23.04.2008 [21:37:09 +0200], Andi Kleen wrote:

<snip>

>  - How to deal with archs with many hugepage sizes available (IA64?) Do
>    we show all of them in /proc/meminfo?

Hrmm, IA64 here may be a red herring. As I understand it, with short
VHPT mode, there is one hugepage size for all of the hugepage region. In
which case, I think, we'd just make IA64 special in that the first
hugepagesz specified is the one used (and the only visible) or whatever
is the current native default with hugepages= is the one visible
(256M?). That is, IA64 will always only have one hugepagesize available
at run-time on a given boot, so we only need to show the one set of
files in /proc/meminfo. If IA64 moves to long VHPT mode, things would
need adjusting, I guess.

Clearly, we want to document this in kernel-parameters.txt :)

We also should bring in the sparc and sh maintainers, in case they want
to chime in on how things might be presented to those architectures, if
they want to move to multiple hugepage pools?

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