> Another problem with X which cannot be fixed is out-of-memory killing
> and restoration of state.
>
> The solution?
> 1) reliable X servers
> 2) video cards which you don't need to know the state for!
3) don't kill random processes when out of memory, instead, make
a careful selection and don't kill processes that have CAP_RAW_IO
set
Of course, this gives problems when X _is_ running wild, but
then you're out of luck anyway.
I'm working on my OOM killing patch again (after receiving some
valueable input on when to start killing) and it should/might/could
be ready this weekend...
Together with the 'swapd' swap-on-demand program you could
actually build a Linux box that's considerably harder to
kill than it is now.
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
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.altern.org/andrebalsa/doc/lkml-faq.html