Re: OOM?

From: Chris Wedgwood (cw@f00f.org)
Date: Mon Jun 26 2000 - 16:24:27 EST

Next message: Lennert Buytenhek: "Re: [question] Linux read/write spinlocks and readers starving a writer"
Previous message: Alan Cox: "Linux 2.4.0-test2-ac2"
In reply to: David Whysong: "Re: OOM?"
Next in thread: Andrea Arcangeli: "Re: OOM?"
Reply: Andrea Arcangeli: "Re: OOM?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

But init often does die. I've seen it happen, more than once.

Since you normally have a fair amount of free memory, you could hack
init to do an mlockall(MCL_CURRENT|MCL_FUTURE).

--cw

-
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/

Next message: Lennert Buytenhek: "Re: [question] Linux read/write spinlocks and readers starving a writer"
Previous message: Alan Cox: "Linux 2.4.0-test2-ac2"
In reply to: David Whysong: "Re: OOM?"
Next in thread: Andrea Arcangeli: "Re: OOM?"
Reply: Andrea Arcangeli: "Re: OOM?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:09 EST