On Monday 10 October 2005 08:51, Chen, Kenneth W wrote:
> Demand paging is one aspect of enhancing generality of hugetlb. Intel
> initially proposed the feature 18 month ago [* see link below] along
> with SGI. Christoph Lameter at SGI scratched that subject Oct 2004.
> And now, Adam at IBM attempts it again. There is a growing need to
> make hugetlb easier to use, more transparency in using hugetlb pages
> etc. All requires hugetlb code to be more generalized, instead of
> reducing functionality.
It's also badly needed to make hugetlbfs NUMA policy aware. mbind
requires allocation on demand, because it runs after mmap and
cannot fix up the policy when the pages are already allocated.
> Granted, the patch I posted on expanding ftruncate will be replaced
> once demand paging goes in. I wanted to demonstrate that it is a
> feature we should implement, instead of cutting back more on current
> thin functionality in hugetlbfs. (with demand paging, expanding
> ftruncate should be really easy and clean, instead of "peculiar
> semantics" all because of prefaulting).
I would like to have it. I remember hating to implement extending
truncate by hand when I did the test programs for the hugetlbfs numa policy.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]