From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
linux-kernel@vger.kernel.org
Subject: Re: queue_nr_requests needs to be selective
Date: Sat, 2 Mar 2002 10:10:23 +0100 [thread overview]
Message-ID: <20020302091023.GH12014@suse.de> (raw)
In-Reply-To: <20020301132254.A11528@vger.timpanogas.org> <3C7FE7DD.98121E87@zip.com.au> <20020301162016.A12413@vger.timpanogas.org> <3C800D66.F613BBAA@zip.com.au> <20020301172701.A12718@vger.timpanogas.org> <3C8021A9.BB16E3FC@zip.com.au> <20020301191626.A13313@vger.timpanogas.org> <3C804BF0.3993B153@zip.com.au>
In-Reply-To: <3C804BF0.3993B153@zip.com.au>
On Fri, Mar 01 2002, Andrew Morton wrote:
> So it would be more straightforward to just allow the queue
> to be grown later on?
I agree with that too. I'm fine with the patch, I'm just a bit worried
about the batch_request vs nr_requests ratio. Are you sure 1/4 is always
a good ratio? In my previous testing, a batch value of more than 32 had
little impact and usually changed things for the worse.
--
Jens Axboe
next prev parent reply other threads:[~2002-03-02 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 20:22 queue_nr_requests needs to be selective Jeff V. Merkey
2002-03-01 20:43 ` Andrew Morton
2002-03-01 21:03 ` Alan Cox
2002-03-01 23:22 ` Jeff V. Merkey
2002-03-01 23:20 ` Jeff V. Merkey
2002-03-01 23:23 ` Andrew Morton
2002-03-02 0:27 ` Jeff V. Merkey
2002-03-02 0:49 ` Andrew Morton
2002-03-02 2:16 ` Jeff V. Merkey
2002-03-02 3:50 ` Andrew Morton
2002-03-02 4:34 ` Jeff V. Merkey
2002-03-02 7:33 ` Jeff V. Merkey
2002-03-02 9:10 ` Jens Axboe [this message]
2002-03-02 9:22 ` Andrew Morton
2002-03-04 9:09 ` Jens Axboe
2002-03-02 0:51 ` Mike Anderson
2002-03-02 4:39 ` Jeff V. Merkey
2002-03-02 5:59 ` Jeff V. Merkey
2002-03-02 6:01 ` Jeff V. Merkey
2002-03-02 6:16 ` Jeff V. Merkey
2002-03-04 7:16 ` Mike Anderson
2002-03-04 17:39 ` 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=20020302091023.GH12014@suse.de \
--to=axboe@suse.de \
--cc=akpm@zip.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox