From: Robert Love <rml@tech9.net>
To: Neil Schemenauer <nas@python.ca>
Cc: Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [PATCH][CFT] new IO scheduler for 2.4.20
Date: 30 May 2003 17:58:21 +0000 [thread overview]
Message-ID: <1054317501.15356.2183.camel@localhost> (raw)
In-Reply-To: <20030531005247.GA646@glacier.arctrix.com>
On Sat, 2003-05-31 at 00:52, Neil Schemenauer wrote:
> I didn't change the size of the request queue. I can't find where that
> gets set in 2.4.20. :-(
in drivers/block/ll_rw_blk.c :: blk_init_free_list()
I think the main reason (aside from memory consumption) 2.4 has such
small queues is to minimize read latency. If your patch goes off fixes
that, you can probably get away with larger queues, which will help in
merging. But then you definitely want to look into always merging reads,
like Andrew does.
A maximum of ~1000 request entries seems nice if you really give a boost
to reads otherwise.
Robert Love
next prev parent reply other threads:[~2003-05-31 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 22:09 [PATCH][CFT] new IO scheduler for 2.4.20 Neil Schemenauer
2003-05-30 23:40 ` Con Kolivas
2003-05-31 0:52 ` Neil Schemenauer
2003-05-30 17:58 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-02 17:21 Andreas Dilger
2003-04-17 17:28 Neil Schemenauer
2003-04-17 20:41 ` Andrew Morton
2003-04-20 18:26 ` Neil Schemenauer
2003-04-20 22:06 ` Marc-Christian Petersen
2003-04-21 1:46 ` Neil Schemenauer
2003-04-21 11:33 ` Andrea Arcangeli
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=1054317501.15356.2183.camel@localhost \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nas@python.ca \
/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