Re: /tmp in swap space

Rik van Riel (H.H.vanRiel@phys.uu.nl)
Tue, 26 May 1998 13:19:47 +0200 (MET DST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Rik van Riel: "Re: Linux-2.0.34 & crashme"
Previous message: Alan Cox: "Re: cpu misdetection"

On Mon, 25 May 1998, Jelle Foks wrote:
> On Mon, 25 May 1998 linker@nightshade.ml.org wrote:
>
> > I think that when the system runs out of mem+swap it starts thrashing then
> > kills off processes biggest first (and for alot of unhappy folks, that
> > usually is X which ends up killing all their X apps, and sometimes leaving
> > the console unusable). Or perhaps they only die when they try to allocate
> > more.
>
> Unless we look a bit more carefully to find the process (or parent-child
> chain of processes) that has been growing with the fastest rate in the
> last few seconds. Maybe also use the time that a process has been running,
> which works if we can assume that processes that have been around for a
> while can be 'trusted' not to be the wrongdoers. In case of a process
> going bezerk (on purpose or not), this type of rules will mean the bezerk
> process will be asked to leave, not just the largest process.

Look on my homepage for a draft version of the killing
and selecting code. The only code that's still missing
is the code that decides when to call the killing code.

The file is oom_kill.c in the patches directory...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Rik van Riel: "Re: Linux-2.0.34 & crashme"
Previous message: Alan Cox: "Re: cpu misdetection"