From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Marc-Christian Petersen <m.c.p@wolk-project.de>,
linux-kernel@vger.kernel.org, Con Kolivas <conman@kolivas.net>
Subject: Re: [PATCH] 2.4.20-rmap15a
Date: Mon, 2 Dec 2002 09:56:10 +0100 [thread overview]
Message-ID: <20021202085610.GU16942@suse.de> (raw)
In-Reply-To: <3DEB1F2C.E03517D7@digeo.com>
On Mon, Dec 02 2002, Andrew Morton wrote:
> Jens Axboe wrote:
> >
> > On Sun, Dec 01 2002, Rik van Riel wrote:
> > > > So, here my patch proposal. Ontop of 2.4.20-rmap15a.
> > >
> > > Looks good, now lets test it. If the patch is as needed as you
> > > say we should push it to marcelo ;)
> >
> > Yes lets for heavens sake not fix the problem, merge the hack.
>
> If it fails to find a merge or insert the current 2.4 elevator
> will stick a read at the far end of the request queue. That's
> quite arbitrary, and is the worst possible thing to do with it.
>
> read-latency2 will put the read a tunable distance from the head.
> Add a few embellishments to avoid permanent writer starvation,
> and that's basically all it does.
I just think that the design of the thing is ugly. It's clamped on to
the current elevator instead of redoing the core based on the principles
of read-starvation that it introduces (this is the only good thing that
has come out of the patch).
> So rather than just keeping on calling it a "hack" could you please
> describe what is actually wrong with the idea?
I've never said that the idea is wrong, it's the solution that is an
ugly hack.
--
Jens Axboe
next prev parent reply other threads:[~2002-12-02 8:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 20:56 [PATCH] 2.4.20-rmap15a Marc-Christian Petersen
2002-12-01 21:25 ` Rik van Riel
2002-12-01 21:41 ` Marc-Christian Petersen
2002-12-01 21:56 ` Con Kolivas
2002-12-02 0:18 ` Con Kolivas
2002-12-02 8:15 ` Jens Axboe
2002-12-02 8:51 ` Andrew Morton
2002-12-02 8:56 ` Jens Axboe [this message]
2002-12-02 12:38 ` Rik van Riel
2002-12-02 20:45 ` Willy Tarreau
2002-12-02 23:10 ` Rik van Riel
2002-12-03 6:21 ` Willy Tarreau
2002-12-02 21:46 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 20:35 Rik van Riel
2002-12-01 20:35 ` Rik van Riel
2002-12-03 13:55 ` Miquel van Smoorenburg
2002-12-03 16:39 ` Sean Neakums
2002-12-03 19:58 ` The One True Dave Barry
2002-12-03 20:08 ` Martin J. Bligh
2002-12-03 20:56 ` Rik van Riel
2002-12-04 11:28 ` Sean Neakums
2002-12-04 13:33 ` Sean Neakums
2002-12-04 11:40 ` Arjan van de Ven
2002-12-04 12:12 ` Rik van Riel
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=20021202085610.GU16942@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=riel@conectiva.com.br \
/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.