From: Jens Axboe <axboe@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Karl Vogel <karl.vogel@seagha.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Kernel 2.6.8.1: swap storm of death - CFQ scheduler=culprit
Date: Tue, 24 Aug 2004 12:52:43 +0200 [thread overview]
Message-ID: <20040824105242.GO2355@suse.de> (raw)
In-Reply-To: <20040824091859.GA6961@logos.cnet>
On Tue, Aug 24 2004, Marcelo Tosatti wrote:
> On Tue, Aug 24, 2004 at 12:03:43PM +0200, Jens Axboe wrote:
> > On Mon, Aug 23 2004, Karl Vogel wrote:
> > > > > Jens, is this huge amount of bio/biovec's allocations
> > > > expected with CFQ? Its really really bad.
> > > >
> > > > Nope, it's not by design :-)
> > > >
> > > > A test case would be nice, then I'll fix it as soon as possible. But
> > > > please retest with 2.6.8.1 marcelo, 2.6.8-rc4 is missing an important
> > > > fix to ll_rw_blk that can easily cause this. The first report is for
> > > > 2.6.8.1, so I'm more puzzled on that.
> > >
> > > I tried with 2.6.8.1 and 2.6.8.1-mm4, both had the problem. If there
> > > is anything extra I need to try/record, just shoot!
> > >
> > > Original post with testcase + stats:
> > > http://article.gmane.org/gmane.linux.kernel/228156
> >
> > 2.6.8.1-mm4 clean does not reproduce the problem. Marcelo, your
> > 2.6.8-rc4 report is not valid due to the fixed problem related to that
> > in CFQ already. I'd still like for you to retest with 2.6.8.1.
> >
> > So I'm trying 2.6.8.1 with voluntary preempt applied now, the bug could
> > be related to that.
>
> Jens,
>
> You are right, I've been unable to reproduce the problem I was seeing
> (huge amount of bio/biovec's allocation causing major swapouts) with
> 2.6.8.1.
>
> With this kernel, The 512MB system swaps around 50MB and recovers perfectly,
> I can't see any odd behaviour with CFQ.
Great, thanks for verifying. So that just leaves this other problem,
once traces of hung processes are generated we'll know more. Currently I
cannot reproduce it with 2.6.8.1-mm4 at all, enabling preempt did
nothing to help it.
--
Jens Axboe
next prev parent reply other threads:[~2004-08-24 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 16:10 Kernel 2.6.8.1: swap storm of death - CFQ scheduler=culprit Karl Vogel
2004-08-23 17:00 ` Jens Axboe
2004-08-24 10:03 ` Jens Axboe
2004-08-24 9:18 ` Marcelo Tosatti
2004-08-24 10:52 ` Jens Axboe [this message]
2004-08-24 10:13 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 10:35 Karl Vogel
2004-08-24 10:28 Karl Vogel
2004-08-24 10:29 ` Jens Axboe
2004-08-22 13:27 Kernel 2.6.8.1: swap storm of death Karl Vogel
2004-08-22 18:49 ` Kernel 2.6.8.1: swap storm of death - 2.6.8.1-mm4 also karl.vogel
2004-08-22 19:18 ` Kernel 2.6.8.1: swap storm of death - CFQ scheduler=culprit Karl Vogel
2004-08-23 14:12 ` Marcelo Tosatti
2004-08-23 15:41 ` Jens Axboe
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=20040824105242.GO2355@suse.de \
--to=axboe@suse.de \
--cc=karl.vogel@seagha.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.