From: Jens Axboe <axboe@suse.de>
To: Dipankar Sarma <dipankar@sequent.com>
Cc: Mike Anderson <mike.anderson@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: io_request_lock patch?
Date: Wed, 11 Jul 2001 21:16:15 +0200 [thread overview]
Message-ID: <20010711211615.G712@suse.de> (raw)
In-Reply-To: <20010710172545.A8185@in.ibm.com> <20010710160512.A25632@us.ibm.com> <20010711142311.B9220@in.ibm.com> <20010711105339.F17314@suse.de> <20010711193256.G9220@in.ibm.com> <20010711160148.A712@suse.de> <20010711202536.H9220@in.ibm.com>
In-Reply-To: <20010711202536.H9220@in.ibm.com>
On Wed, Jul 11 2001, Dipankar Sarma wrote:
> On Wed, Jul 11, 2001 at 04:01:48PM +0200, Jens Axboe wrote:
> > On Wed, Jul 11 2001, Dipankar Sarma wrote:
> > > On Wed, Jul 11, 2001 at 10:53:39AM +0200, Jens Axboe wrote:
> > > > The queue lengths should always be long enough to keep the hw busy of
> > > > course. And in addition, the bigger the queues the bigger the chance of
> > > > skipping seeks due to reordering. But don't worry, I've scaled the queue
> > > > lengths so I'm pretty sure that they are always on the safe side in
> > > > size.
> > > >
> > > > It's pretty easy to test for yourself if you want, just change
> > > > QUEUE_NR_REQUESTS in blkdev.h. It's currently 8192, the request slots
> > > > are scaled down from this value. 8k will give you twice the amount of
> > > > slots that you have RAM in mb, ie 2048 on a 1gig machine.
> > > >
> > > > block: queued sectors max/low 683554kB/552482kB, 2048 slots per queue
> > >
> > > Hmm.. The tiobench run was done on a 1GB machine and we still ran
> > > out of request slots. Will investigate.
> >
> > Sure, that's to be expected. If we never ran out we would be wasting
> > memory. My point is that you should rerun the same test with more
> > request slots -- and I'd be surprised if you gained any significant
> > performance on that account. I never said that you'd never run out,
> > that's of course not true. In fact, running out is what starts the I/O
> > typically on a 1GB machine and bigger.
>
> I agree that running out of slots don't necessarily mean anything. I
> was just wondering about the queue lengths. On the face of it, 2048
> requests pending for a single disk seems like a fairly large queue length.
> Is this all related to plugging of queues for disk block optimization ?
Plugging to a degree, although when you get queues this long you can
get nice merging even though the queue will probably never get replugged
(because it never empties). The merging is the most important step, and
also the insertion sort of course.
--
Jens Axboe
next prev parent reply other threads:[~2001-07-11 19:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 11:55 io_request_lock patch? Dipankar Sarma
2001-07-10 23:05 ` Mike Anderson
2001-07-11 7:15 ` Jens Axboe
2001-07-11 8:53 ` Dipankar Sarma
2001-07-11 8:53 ` Jens Axboe
2001-07-11 14:02 ` Dipankar Sarma
2001-07-11 14:01 ` Jens Axboe
2001-07-11 14:55 ` Dipankar Sarma
2001-07-11 19:16 ` Jens Axboe [this message]
2001-07-11 16:02 ` Mike Anderson
2001-07-11 19:20 ` Jens Axboe
2001-07-11 20:13 ` Dipankar Sarma
2001-07-11 20:17 ` Jens Axboe
2001-07-11 21:05 ` Mike Anderson
2001-07-11 7:19 ` Jens Axboe
2001-07-11 8:39 ` Dipankar Sarma
2001-07-11 8:47 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-07-09 19:39 Jonathan Lahr
2001-07-09 19:44 ` Jens Axboe
2001-07-10 19:49 ` Jonathan Lahr
2001-07-10 20:09 ` Eric Youngdale
2001-07-11 8:05 ` Jens Axboe
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=20010711211615.G712@suse.de \
--to=axboe@suse.de \
--cc=dipankar@sequent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.anderson@us.ibm.com \
/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