From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Chris Johns <cbjohns@mn.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kswapd excessive CPU time
Date: Wed, 9 Jun 2004 15:05:14 -0300 [thread overview]
Message-ID: <20040609180514.GA5859@logos.cnet> (raw)
In-Reply-To: <510EDE3E-B962-11D8-B170-000A958E2366@mn.rr.com>
On Tue, Jun 08, 2004 at 10:41:32AM -0500, Chris Johns wrote:
> On a 2.4.21 kernel (kernel.org + KDB patch + MITRE security patches),
> I've seen bizarre (I think) behavior from kswapd.
>
> My question boils down to this: given the (simple) scenario below,
> am I missing critical VM/kswapd patches, or is this behavior
> expected and OK, or is it wrong and possibly fixed in the 2.6 kernel?
> Or is the kswapd behavior somehow tunable to avoid the apparent
> thrashing that I saw?
Recent 2.4 VM should fix this, but you better of use 2.6.
next prev parent reply other threads:[~2004-06-09 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 15:41 kswapd excessive CPU time Chris Johns
2004-06-09 18:05 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 19:23 cbjohns
2004-06-10 0:49 ` Marcelo Tosatti
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=20040609180514.GA5859@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=cbjohns@mn.rr.com \
--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