public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: tglx@linutronix.de
Cc: Chris Ross <chris@tebibyte.org>,
	Chris Friesen <cfriesen@nortelnetworks.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.9-ac16
Date: Sat, 18 Dec 2004 10:11:55 -0500	[thread overview]
Message-ID: <41C448BB.1020902@tmr.com> (raw)
In-Reply-To: <1103349675.27708.39.camel@tglx.tec.linutronix.de>

Thomas Gleixner wrote:

> Andrea fixed the invocation problem, which also handles the reentrancy
> problem in a clean way. It get's us rid of the ugly count, time,
> whatever mechanisms in out_of_memory which was designed to cover the
> invocation problem but was not able to prevent reentrancy and the
> resulting overkill (kill a random amount of processes even if enough
> memory is available). 
> 
> I added the "Take child processes into account" modification for the
> whom to kill selection on top of that and I was not able to make it
> missbehave with my different test scenarios.
> 
> The patches are available in parts in this thread and the final combined
> patch is there:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110269783227867&w=2
> 
> 2.6.10-rc3 contains a partial fix for the erroneous invocation problem,
> but it is not as effective as Andrea's solution and it still runs into
> overkill once the oom mechanism is invoked.
> 
> Andrea's fix and the selection changes should go into 2.6.10, but I
> suspect that the VM gurus havent still reached a point, where they
> agree. I also have the feeling that the problem is partially ignored.
> Obviously has everybody plenty of memory in his boxes. </rant off>

As someone who runs most new versions first on a 96MB (slow) machine, I 
would agree that this is a desirable change. I'm not sure yet if the 
selection is optimal, but it's better than the stock kernel, which seems 
to follow the "kill them all, let god sort it out" principle.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  reply	other threads:[~2004-12-18 15:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 18:43 Linux 2.6.9-ac16 Alan Cox
2004-12-17 11:23 ` Arjan van de Ven
2004-12-17 18:54   ` Francois Romieu
2004-12-17 13:08 ` Chris Ross
2004-12-17 14:51   ` Chris Friesen
2004-12-17 15:45     ` Chris Ross
2004-12-18  6:01       ` Thomas Gleixner
2004-12-18 15:11         ` Bill Davidsen [this message]
2004-12-18 15:06           ` Jan Engelhardt
2004-12-18 16:01             ` Chris Ross
2004-12-20 14:48             ` Alan Cox
2004-12-20 16:19               ` Chris Ross
2004-12-20 19:54                 ` Alan Cox
2004-12-19 16:22           ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2004-12-17 23:35 Chuck Ebbert
2004-12-20 17:27 ` Chris Friesen
2004-12-21  9:11 Chuck Ebbert
2004-12-21 23:49 Chuck Ebbert
2004-12-21 23:58 ` Nick Piggin
2004-12-22  2:49 ` Con Kolivas
2004-12-22  6:44 Chuck Ebbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41C448BB.1020902@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cfriesen@nortelnetworks.com \
    --cc=chris@tebibyte.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox