Andrew wrote:
> If it's per-cpuset information then shouldn't it be presented in
> /dev/cpuset/something?
Yeah - if huge pages were mainline future, rather than the more
controversial sideline they are now, then it would make more sense
to put in these stats in each cpuset.
Note, Ken, that if we did that, the calculation of these new Total and
Free stats would be a little different than your new code. Instead of
looping over the memory nodes in the current tasks mems_allowed mask,
we would loop over the memory nodes allowed in the cpuset being queried
(the cpuset whose 'hugepages_total' or 'hugepages_free' special
file we were reading, not the current tasks cpuset.)
But I'm reluctant to entertain such cpuset additions until I see more
of where my colleague Christoph is going in related work.
Clearly as can be seen on one of his posts on the parallel lkml thread:
Re: + pretend-cpuset-has-some-form-of-hugetlb-page-reservation.patch added to -mm tree
earlier today, Christoph is no great fan of the current implementation
of huge pages.
And clearly as memory continues to get bigger, we will be putting more
stress on these page size related mechanisms.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
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]
