Is there any way to make the global limits on which the dirty rate
calculations are based cpuset specific?
A process is part of a cpuset and that cpuset has only a fraction of
memory of the whole system.
And only a fraction of that fraction can be dirtied. We do not currently
enforce such limits which can cause the amount of dirty pages in
cpusets to become excessively high. I have posted several patchsets that
deal with that issue. See http://lkml.org/lkml/2007/1/16/5
It seems that limiting dirty pages in cpusets may be much easier to
realize in the context of this patchset. The tracking of the dirty pages
per node is not necessary if one would calculate the maximum amount of
dirtyable pages in a cpuset and use that as a base, right?
-
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]
