Re: [Patch] cpusets policy kill no swap

Thanks Andrew - you're right. Drop this patch in /dev/null. * I will look around for some way that user code can detect that a task has provoked swapping, or propose a small patch, perhaps to /proc, for that, if need be. * I agree that the action, killing a task or whatever, can and s

Re: [Patch] cpusets policy kill no swap

Interesting comments, Andrew. Thanks It will likely be a couple of days before I respond to them. I suspect a couple of us SGI folks should powwow first. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <[EM

Re: [Patch] cpusets policy kill no swap

Paul Jackson <[EMAIL PROTECTED]> wrote: > > This mechanisms differs from a general purpose out-of-memory > killer in various ways, including: > > * An oom-killer tries to score the bad buy, to avoid shooting > the innocent little task that just happened to ask for one > page too many. >

[Patch] cpusets policy kill no swap

Question: Should I call oom_kill_process(), oom_kill_task(), or __oom_kill_task(), when the current task decides that it is better to die than to swap, so calls the routine mm/oom_kill.c:oom_attempt_suicide() that this patch adds, below? My best gue