From: Jens Axboe <axboe@suse.de>
To: "Jeff V. Merkey" <jmerkey@drdos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: submit_bh leaves interrupts on upon return
Date: Thu, 3 Jun 2004 19:03:28 +0200 [thread overview]
Message-ID: <20040603170328.GQ1946@suse.de> (raw)
In-Reply-To: <40BF9124.6080807@drdos.com>
On Thu, Jun 03 2004, Jeff V. Merkey wrote:
> Jens Axboe wrote:
>
> >Submitting large numbers of buffer_heads from b_end_io is _nasty_, 2.4
> >io scheduler runtime isn't exactly world champion and you are doing this
> >at hard irq time. Not a good idea. Definitely not the true path to
> >performance, unless you don't care about anything else in the system.
> >
> >At least in 2.6 you have a much faster io scheduler and the additionally
> >large bio, so you wont spend nearly as much time there if you are
> >clever. You still need process context, though, that hasn't changed.
> >
> >
> >
> Sounds like I need to move to 2.6. I noticed the elevator is coalescing
> quite well, and since I am posting mostly continguous runs of sectors,
> what ends up at the adapter level would probably not change much much
> between 2.4 and 2.6 since I am maxing out the driver request queues as
> it is (255 pending requests of 32 scatter/gather elements of 256 sector
> runs). 2.6 might help but I suspect it will only help alleviate the
> submission overhead, and not make much difference on performance since
> the 3Ware card does have an upward limit on outstanding I/O requests.
That's correct, it just helps you diminish the submission overhead by
pushing down 256 sector entities in one go. So as long as you're io
bound it won't give you better io performance, of course. If you are
doing 400MiB/sec it should help you out, though.
--
Jens Axboe
next prev parent reply other threads:[~2004-06-03 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:58 submit_bh leaves interrupts on upon return Jeff V. Merkey
2004-06-03 8:50 ` Jens Axboe
2004-06-03 20:46 ` Jeff V. Merkey
2004-06-03 16:52 ` Jens Axboe
2004-06-03 20:59 ` Jeff V. Merkey
2004-06-03 17:03 ` Jens Axboe [this message]
2004-06-03 17:26 ` Linus Torvalds
2004-06-03 17:34 ` Jens Axboe
2004-06-03 23:56 ` Jeff V. Merkey
2004-06-03 21:17 ` 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=20040603170328.GQ1946@suse.de \
--to=axboe@suse.de \
--cc=jmerkey@drdos.com \
--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