public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 4 Mar 2002 10:09:25 +0100	[thread overview]
Message-ID: <20020304090925.GC1062@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> <20020302091023.GH12014@suse.de> <3C8099BF.85BA994D@zip.com.au>
In-Reply-To: <3C8099BF.85BA994D@zip.com.au>

On Sat, Mar 02 2002, Andrew Morton wrote:
> > 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.
> > 
> 
> Well I just left it as it was for the default case...
> 
> I haven't tested much at all for different batching levels.  And
> in this area, tuning it for my combination of hardware probably
> doesn't carry much relevance for Jeff's setup (for example).

Just the fact that you are using much bigger free queue sizes now means
that the batching in itself has less of an effect than with the smaller
queue sizes (here it's absolutely vital to get good merging).

> And the change to FIFO wakeup may have invalidated your earlier
> testing.

Could be, I'd inclined to think that FIFO behaviour would aid the
batching as well. Remember that we have had FIFO wakups there before, so
that's not entirely new.

> So hmm.  I'll have a play with it, and if nothing obvious jumps
> out, I'll just clamp it at 32.

I think that would be best, I'll wait for numbers though :-). To be
honest, batch counts of eg 256 just sounds a bit insane to me.

-- 
Jens Axboe


  reply	other threads:[~2002-03-04  9:12 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
2002-03-02  9:22                 ` Andrew Morton
2002-03-04  9:09                   ` Jens Axboe [this message]
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=20020304090925.GC1062@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