On Mon, Feb 26, 2007 at 03:21:26PM -0800, Nishanth Aravamudan wrote:
> Author: Nishanth Aravamudan <[EMAIL PROTECTED]>
> Date: Mon Feb 26 15:17:54 2007 -0800
>
> hugeutils: add address parameter to hugetlbfs_vaddr_granularity
>
> On ppc64, the actual granularity of hugepage requests depends on the
> address in question. Specify the three cases (0-4G, 4G-1TB, 1TB+) in the
> function. This is useful for the partial_remap code, as it would
> (effectively) never run on ppc64 otherwise (would need a 1TB or larger
> segment, without relinking).
I've thought about doing something like this before. However, the
semantics as they stand are a little bit fuzzy. What I'd prefer, if
you want to get finer-grained information about the page-size regions
is a pair of functions to find the end and beginning of a page-size
slice, given an address. So:
void *hugetlbfs_slice_end(void *addr);
void *hugetlbfs_slice_start(void *addr);
The "slice" terminology is something BenH has started using for these
address space regionsin some recent kernel patches.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Libhugetlbfs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
