Messages in this thread | | | Subject | Re: Linux machines dieing in swap storms | From | Richard Purdie <> | Date | Thu, 25 Oct 2007 19:28:20 +0100 |
| |
On Thu, 2007-10-25 at 17:13 +0100, Alan Cox wrote: > > I'm seriously tempted to add a "kill the process using the most memory" > > key combination into SysRq which might let me save the desktop but won't > > help with my remote server. I could also just disable swap I guess. > > For specific applications you can set resource limits, you can also set > OOM priorities in current kernels to pick who dies.
I couldn't seem to find much documentation on this. For the archive and to confirm we're talking about the same thing, you mean:
echo 10 > /proc/PID/oom_adj
(and ulimit/setrlimit for the resource limits) ?
This assumes I know in advance which processes are likely to go mad which isn't ideal although it could solve my immediate problem.
> Finally you can disable overcommit and go for a rigid "no overcommit" > policy where the system will fail any memory allocation which might lead > to out of memory situations later.
Its certainly another option but other processes then suffer because certain applications have bugs in them?
Thanks,
Richard
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |