public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Petersen <Chris.Petersen@synopsys.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Chris Petersen <Chris.Petersen@synopsys.COM>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: FIXED (was Re: PROBLEM:  Blk Dev Cache causing kswapd thrashing)
Date: Wed, 10 Dec 2003 12:44:42 -0500	[thread overview]
Message-ID: <3FD75B8A.21FA59D9@synopsys.com> (raw)
In-Reply-To: Pine.LNX.4.44.0311271649520.21568-100000@logos.cnet

Marcelo,

It appears the block-device-cache/kswapd problem is indeed fixed in
2.4.23 (yay!).

To confuse matters RedHat has released an RPM with 2.4.20-24.7 which
apparently contains later patches that include the fix.  This can be
confusing because their 2.4.21-4EL kernel is busted (WRT this bug).
But, at least this way we can simply tell our RH-based customers to go
grab the RPM.

Thanks,
-chris

Marcelo Tosatti wrote:
> 
> On Tue, 25 Nov 2003, William Lee Irwin III wrote:
> 
> > On Tue, Nov 25, 2003 at 04:03:56PM -0500, Chris Petersen wrote:
> > > The block device cache is causing kswapd thrashing, usually bringing
> > > the system to a halt.
> > > This problem has been reproduced on kernels as recent as 2.4.21.
> > > In our application we deal with large (multi-GB) files on multi-CPU
> > > 4GB platforms.  While handling these files, the block device cache
> > > allocates all remaining available memory (3.5G) up to the 4G
> > > physical limit.
> >
> > Please try 2.4.23-rc5, and if that doesn't fix it, try 2.6.0-test10.
> > AIUI both have page replacement improvements over 2.4.21.
> 
> Chris,
> 
> Did you try 2.4 already?
> 
> If you didnt, please tell me results when you do so.
> 
> Thanks

-- 
-----------------------------------------------------------------
Chris M. Petersen                                cmp@synopsys.com
Sr. R&D Engineer

Synopsys, Inc.                                    o: 919.425.7342
1101 Slater Road, Suite 300                       c: 919.349.6393
Durham, NC  27703                                 f: 919.425.7320
-----------------------------------------------------------------

       reply	other threads:[~2003-12-10 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0311271649520.21568-100000@logos.cnet>
2003-12-10 17:44 ` Chris Petersen [this message]
2003-12-10 18:08   ` FIXED (was Re: PROBLEM: Blk Dev Cache causing kswapd thrashing) Dave Jones
2003-12-10 19:01     ` Chris Petersen
2003-12-10 19:16       ` Dave Jones

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=3FD75B8A.21FA59D9@synopsys.com \
    --to=chris.petersen@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=wli@holomorphy.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