From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: General 2.4 impressions (was Re: [PATCH] Prevent OOM from killing init)
Date: Fri, 23 Mar 2001 10:13:55 -0500 [thread overview]
Message-ID: <3ABB6833.183E9188@mandrakesoft.com> (raw)
In-Reply-To: <m1hf0k1qvi.fsf@frodo.biederman.org>
Personally I think the OOM killer itself is fine. I think there are
problems elsewhere which are triggering the OOM killer when it should
not be triggered, ie. a leak like Doug Ledford was reporting.
I definitely see heavier page/dcache usage in 2.4 -- but that is to be
expected due to 2.4 changes! So it is incredibily difficult to quantify
if something is wrong, and if so, where...
My own impressions of 2.4 are that it "feels faster" for my own uses and
it's stable. The downsides I find are that heavy fs activity seems to
imply increased swapping, which jibes with a guess that the page/dcache
is exceptionally greedy with releasing pages under memory pressure.
</unquantified vague ramble>
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-03-23 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010323015358Z129164-406+3041@vger.kernel.org>
2001-03-23 7:04 ` [PATCH] Prevent OOM from killing init Rik van Riel
2001-03-23 11:28 ` Guest section DW
2001-03-23 14:50 ` Eric W. Biederman
2001-03-23 15:13 ` Jeff Garzik [this message]
2001-03-23 16:10 ` Adding just a pinch of icache/dcache pressure Jan Harkes
2001-03-23 16:17 ` Andi Kleen
2001-03-23 17:21 ` [PATCH] Prevent OOM from killing init Guest section DW
2001-03-23 20:18 ` Paul Jakma
2001-03-24 20:19 ` Jesse Pollard
2001-03-23 23:48 ` Eric W. Biederman
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=3ABB6833.183E9188@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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