On Tue, 5 Jun 2007, Christoph Lameter wrote:
> Exclusive is not as absolute as you may think. There is also the
> GFP_KERNEL exception.
>
Memory exclusivity with respect to cpusets should guarantee that memory
nodes do not overlap with siblings if they are marked with mems_exclusive.
The patch simply preserves that behavior through the time period between
when the OOM killer issues a SIGKILL and the task is exiting and marked
with PF_EXITING.
Obviously GFP_KERNEL allocations can allocate regardless of our memory
exclusivity, but the point is that a job in one exclusive cpuset should
not have the ability to effect the performance (in terms of reclaim and
swap), memory usage, or survival of jobs in other exclusive cpusets
because it was out of memory.
> Processes stuck in D state is another issue with reliability.
>
But it's a reality that we need to respect. It happens and when it does
it has the potential to hamper other cpusets that we setup to be exclusive
themselves.
David
-
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]
