From: Jens Axboe <axboe@suse.de>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: Putrid Elevator Behavior 2.4.18/19
Date: Wed, 27 Mar 2002 08:03:25 +0100 [thread overview]
Message-ID: <20020327070325.GA20703@suse.de> (raw)
In-Reply-To: <20020320120455.A19074@vger.timpanogas.org> <20020320220241.GC29857@matchmail.com> <20020320152008.A19978@vger.timpanogas.org> <20020320152504.B19978@vger.timpanogas.org> <3C9935CA.38E6F56F@zip.com.au> <20020320234552.A21740@vger.timpanogas.org> <20020325181645.A17171@vger.timpanogas.org> <20020326014219.GA3536@matchmail.com> <20020326100330.A20201@vger.timpanogas.org>
On Tue, Mar 26 2002, Jeff V. Merkey wrote:
> >
> > That's good news.
> >
> > Are you still working on the A/B list patch? I'd imagine that it could make
> > several problems easier to fix in the block layer.
> >
>
> Yes. I am asking Darren Major, who wrote the A/B implementation
> in NetWare to review the patch before we submit it. It may affect
> some drivers. We are verifying that the change I instrumented
> will not break anything.
I'm curious how you are doing this cleanly in 2.4. There are lots of
places in the kernel that do direct list management on the queue_head.
Are you adding two separate hidden lists and splicing content to the
queue_head?
2.5 has this done much more cleanly (of course I'm very biased). See the
deadline I/O scheduler patch I've posted before, stuff like this can be
done a lot cleaner there. Internal I/O scheduler structures are
completely hidden from drivers.
--
Jens Axboe
next prev parent reply other threads:[~2002-03-27 7:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 19:04 Putrid Elevator Behavior 2.4.18/19 Jeff V. Merkey
2002-03-20 22:02 ` Mike Fedyk
2002-03-20 22:20 ` Jeff V. Merkey
2002-03-20 22:25 ` Jeff V. Merkey
2002-03-21 1:22 ` Andrew Morton
2002-03-21 6:45 ` Jeff V. Merkey
2002-03-26 1:16 ` Jeff V. Merkey
2002-03-26 1:42 ` Mike Fedyk
2002-03-26 17:03 ` Jeff V. Merkey
2002-03-27 7:03 ` Jens Axboe [this message]
2002-03-27 23:20 ` Jeff V. Merkey
2002-03-26 1:45 ` David Rees
2002-03-26 1:57 ` Mike Fedyk
2002-03-26 17:00 ` Jeff V. Merkey
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=20020327070325.GA20703@suse.de \
--to=axboe@suse.de \
--cc=akpm@zip.com.au \
--cc=jmerkey@timpanogas.org \
--cc=jmerkey@vger.timpanogas.org \
--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 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.