From: Jens Axboe <axboe@suse.de>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [RFC]: performance improvement by coalescing requests?
Date: Tue, 21 Jun 2005 09:28:22 +0200 [thread overview]
Message-ID: <20050621072822.GE9020@suse.de> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B01520F3F@otce2k01.adaptec.com>
On Mon, Jun 20 2005, Salyzyn, Mark wrote:
> Jens Axboe [mailto:axboe@suse.de] writes:
> > You say io, but I guess you mean writes in particular?
>
> Read or writes. One of the test cases was:
>
> dd if=/dev/sda of=/dev/null bs=512b
>
> would break apart into 64 4K reads with no completion dependencies
> between them.
That's a silly test case though, because you are intentionally issuing
io in a really small size. Do you have any real world cases?
If you do
dd if=/dev/zero of=/dev/sda bs=512b
and see lots of small requests, then that would be more strange. Can you
definitely verify this is what happens?
> > Or for any substantial amount of io, you would be queueing it so fast
> > that it should have plenty of time to be merged
> > until the drive sucks them in.
>
> Did I mention that this problem started occurring when we increased the
> aacraid adapter and driver performance last year? We managed to suck the
> requests in faster. Sadly (from the perspective of Adaptec pride in our
> hardware controllers ;-> ), the scsi_merge layer is more efficient at
> coalescing the requests than the adapter's Firmware solely because of
> the PCI bus bandwidth used.
>
> I must admit that the last time I did this instrumented test was in the
> 2.6.3 timeframe with SL9.1. This 'plugging' you are talking about, when
> did it make it into the scsi layer? Sounds like I need to retest,
> certainly a good result of opening my mouth to start this thread.
The plugging is a block layer property, it's been in use for ages (since
at least 2.0, I forget when it was originall introduced).
> > And a few ms should be enough time to queue that amount many many
> > times over.
>
> The adapter can suck in 256 requests within a single ms.
I'm sure it can, I'm also sure that you can queue io orders of magnitude
faster than you can send them to hardware!
--
Jens Axboe
next prev parent reply other threads:[~2005-06-21 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 20:48 [RFC]: performance improvement by coalescing requests? Salyzyn, Mark
2005-06-21 7:28 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 12:05 Salyzyn, Mark
2005-06-21 12:34 ` Jens Axboe
2005-06-20 19:25 Salyzyn, Mark
2005-06-20 20:24 ` Jens Axboe
2005-06-20 21:01 ` Jeff Garzik
2005-06-20 23:21 ` Bryan Henderson
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=20050621072822.GE9020@suse.de \
--to=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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