From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Chris Ross <chris@tebibyte.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-ac16
Date: Fri, 17 Dec 2004 08:51:31 -0600 [thread overview]
Message-ID: <41C2F273.6010707@nortelnetworks.com> (raw)
In-Reply-To: <41C2DA43.9070900@tebibyte.org>
Chris Ross wrote:
>
> Alan Cox escreveu:
>
>> Further small fixes for different minor things. A merge of some of the
>> small
>> cleanups from Fedora work and also the fixes for the igmp and vc holes.
>
>
> This kernel still suffers from the faulty OOM killing troubles of
> vanilla 2.6.9. Could you please pick up at least one of the recent fixes
> for this problem, such as as Rik van Riel's?
Can someone point me to his patch? I've been working on and off to try and get
reasonable OOM behaviour. As it stands, 2.6.10-rc2-mm4 still shows nasty
behaviour in OOM conditions, killing off more tasks than strictly required, and
locking up the system for 10-15secs while doing it.
I'd be much happier doing a quick and dirty scan and knocking off something
*now* rather than locking up the system. Surely it can't take 60 billion cycles
of cpu time to pick a task to kill.
Chris
next prev parent reply other threads:[~2004-12-17 14:51 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 [this message]
2004-12-17 15:45 ` Chris Ross
2004-12-18 6:01 ` Thomas Gleixner
2004-12-18 15:11 ` Bill Davidsen
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=41C2F273.6010707@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@tebibyte.org \
--cc=linux-kernel@vger.kernel.org \
/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