public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cbjohns@mn.rr.com
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kswapd excessive CPU time
Date: Wed, 09 Jun 2004 14:23:58 -0500	[thread overview]
Message-ID: <6feb8721a0.721a06feb8@rdc-kc.rr.com> (raw)

> Recent 2.4 VM should fix this, but you better of use 2.6.
> 

Thanks Marcelo. Do you know of specific patches that have
gone into 2.4 that might fix this? I may be able to just apply them
rather than try a whole new kernel release.

Thanks,

Chris

> > 
> > 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? 
> 



             reply	other threads:[~2004-06-09 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 19:23 cbjohns [this message]
2004-06-10  0:49 ` kswapd excessive CPU time Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08 15:41 Chris Johns
2004-06-09 18:05 ` 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=6feb8721a0.721a06feb8@rdc-kc.rr.com \
    --to=cbjohns@mn.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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