From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Chris Ross <chris@tebibyte.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-ac16
Date: Mon, 20 Dec 2004 11:27:03 -0600 [thread overview]
Message-ID: <41C70B67.7020600@nortelnetworks.com> (raw)
In-Reply-To: <200412171837_MC3-1-9129-C5E@compuserve.com>
Chuck Ebbert wrote:
> Nobody has found an answer for the freezes, which persist even in the latest
> 2.6.10-rc but there's a vm_writeout throttling patch in -ac that I haven't tried.
Heh. Figures. Those freezes are what bothers me most, since I've already got a
patch that protects critical processes from being OOM-killed as long as they're
sane.
I just want an OOM-killer that is FAST and doesn't lock up the machine. I don't
really care what it kills, since it won't be *able* to kill anything really
critical.
Chris
next prev parent reply other threads:[~2004-12-20 17:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 23:35 Linux 2.6.9-ac16 Chuck Ebbert
2004-12-20 17:27 ` Chris Friesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-22 6:44 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-21 9:11 Chuck Ebbert
2004-12-16 18:43 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
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
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=41C70B67.7020600@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=76306.1226@compuserve.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