Messages in this thread | | | From | jmcmullan@linuxcar ... | Subject | Re: OOM in 2.2.14 | Date | 13 Jul 2000 19:00:16 GMT |
| |
Rik van Riel <riel@conectiva.com.br> wrote: > Issueing warnings when we're low on swap is probably a > good idea. Just send in the patch and it'll probably get > integrated...
I'll see if I can whip that up for 2.4.0-testN...
>> Would take a lot of the OOM cruft out of the kernel, and >> would alloe pop-up messages, selectable kill-this-app dialogs, >> AI systems, whatever.
> This is lunacy. If we're out of memory, how can we allocate > the memory to do a pop-up message? And where should that > menu appear? On what console of which user? What if we're > a webserver at 4 AM?
A root-owned daemon that has made sure to lock down any memory it may need via mlock() won't have any swapping issues. Running at nice -20, or even better, FIFO scheduling, you can eat as much (or as little) of a timeslice from other apps as needed.
With this basis, you can have all sorts of flavors of the daemon that do kill processes randomly, ask the user for which process to kill, have a list of ``you can kill any processes but these....' or what have you.
Actually, extending klogd to have a pluggable log-message-to-action filter would be the best general case solution. Then, you could handle missing floppies, automatic Ooops handling, whatever.
Your thoughts?
-- Jason McMullan, Senior Linux Consultant, Linuxcare, Inc. 412.422.8077 tel, 412.656.3519 cell, 415.701.0792 fax jmcmullan@linuxcare.com, http://www.linuxcare.com/ Linuxcare. Support for the revolution.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |