On Tue, 5 Jun 2007, David Rientjes wrote:
> 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.
Right but the process is terminating thus only requiring limited resources
to get finished. The process does not have the ability to affect the other
cpusets. I.e. it cannot directly allocate outside of the cpuset. The
system has that capability and the system is handling the termination of
the process and should terminate the process in a clean way if possible.
> > 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.
The fact that process hang because of some software deficiency is an
exceptional failure scenario. The system in general is not fully
operational anymore anyways. Typically one or the other lock is held which
makes certain kernel functionality inaccessible.
-
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]
