From: Jens Axboe <axboe@suse.de>
To: Karl Vogel <karl.vogel@seagha.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.8.1: swap storm of death - CFQ scheduler=culprit
Date: Mon, 23 Aug 2004 19:00:45 +0200 [thread overview]
Message-ID: <20040823170044.GB24089@suse.de> (raw)
In-Reply-To: <6DED3619289CD311BCEB00508B8E133601A68B13@nt-server2.antwerp.seagha.com>
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
Good report, I'll reproduce it here tomorrow. Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2004-08-23 17:01 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 [this message]
2004-08-24 10:03 ` Jens Axboe
2004-08-24 9:18 ` Marcelo Tosatti
2004-08-24 10:52 ` Jens Axboe
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=20040823170044.GB24089@suse.de \
--to=axboe@suse.de \
--cc=karl.vogel@seagha.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 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.