From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Nick Piggin'" <nickpiggin@yahoo.com.au>, "Jens Axboe" <axboe@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [patch] use cheaper elv_queue_empty when unplug a device
Date: Tue, 29 Mar 2005 11:02:13 -0800 [thread overview]
Message-ID: <200503291902.j2TJ2Dg00724@unix-os.sc.intel.com> (raw)
In-Reply-To: <42491DBE.6020303@yahoo.com.au>
Nick Piggin wrote on Tuesday, March 29, 2005 1:20 AM
> Speaking of which, I've had a few ideas lying around for possible
> performance improvement in the block code.
>
> I haven't used a big disk array (or tried any simulation), but I'll
> attach the patch if you're looking into that area.
>
> linux-2.6-npiggin/drivers/block/ll_rw_blk.c | 63 ++++++++++------------------
> 1 files changed, 23 insertions(+), 40 deletions(-)
>
> diff -puN drivers/block/ll_rw_blk.c~blk-efficient drivers/block/ll_rw_blk.c
> --- linux-2.6/drivers/block/ll_rw_blk.c~blk-efficient 2005-03-29 19:00:07.000000000 +1000
> +++ linux-2.6-npiggin/drivers/block/ll_rw_blk.c 2005-03-29 19:10:45.000000000 +1000
> @@ -2557,7 +2557,7 @@ EXPORT_SYMBOL(__blk_attempt_remerge);
>
> static int __make_request(request_queue_t *q, struct bio *bio)
> {
> - struct request *req, *freereq = NULL;
> + struct request *req;
> int el_ret, rw, nr_sectors, cur_nr_sectors, barrier, err;
> sector_t sector;
>
> @@ -2577,19 +2577,18 @@ static int __make_request(request_queue_
>
> -again:
> spin_lock_irq(q->queue_lock);
>
> if (elv_queue_empty(q)) {
>
....
> +get_rq:
> /*
> - * Grab a free request from the freelist - if that is empty, check
> - * if we are doing read ahead and abort instead of blocking for
> - * a free slot.
> + * Grab a free request. This is might sleep but can not fail.
> + */
> + spin_unlock_irq(q->queue_lock);
> + req = get_request_wait(q, rw);
> + /*
> + * After dropping the lock and possibly sleeping here, our request
> + * may now be mergeable after it had proven unmergeable (above).
> + * We don't worry about that case for efficiency. It won't happen
> + * often, and the elevators are able to handle it.
> */
> -get_rq:
> - if (freereq) {
> - req = freereq;
> - freereq = NULL;
> - } else {
> - spin_unlock_irq(q->queue_lock);
> - if ((freereq = get_request(q, rw, GFP_ATOMIC)) == NULL) {
> - /*
> - * READA bit set
> - */
> - err = -EWOULDBLOCK;
> - if (bio_rw_ahead(bio))
> - goto end_io;
> -
> - freereq = get_request_wait(q, rw);
> - }
> - goto again;
> - }
>
> req->flags |= REQ_CMD;
>
....
> @@ -2693,10 +2675,11 @@ get_rq:
> req->rq_disk = bio->bi_bdev->bd_disk;
> req->start_time = jiffies;
>
> + spin_lock_irq(q->queue_lock);
> + if (elv_queue_empty(q))
> + blk_plug_device(q);
> add_request(q, req);
> out:
> - if (freereq)
> - __blk_put_request(q, freereq);
> if (bio_sync(bio))
> __generic_unplug_device(q);
This part of change in __make_request() is very welcome for enterprise workload.
I have an unpublished version of patch does something similar. I will look through
all other changes in your patch.
prev parent reply other threads:[~2005-03-29 19:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 2:53 Chen, Kenneth W
2005-03-29 8:06 ` Jens Axboe
2005-03-29 9:19 ` Nick Piggin
2005-03-29 9:21 ` Nick Piggin
2005-03-29 9:28 ` Jens Axboe
2005-03-29 9:50 ` Nick Piggin
2005-03-29 10:06 ` Nick Piggin
2005-03-30 0:57 ` Nick Piggin
2005-03-30 8:11 ` Jens Axboe
2005-04-08 9:45 ` Jens Axboe
2005-04-08 9:55 ` Nick Piggin
2005-04-08 10:02 ` Jens Axboe
2005-04-08 10:22 ` Nick Piggin
2005-03-29 10:10 ` Arjan van de Ven
2005-03-29 10:19 ` Jens Axboe
2005-03-29 10:23 ` Nick Piggin
2005-03-29 13:15 ` Jens Axboe
2005-03-30 0:07 ` Nick Piggin
2005-03-29 19:02 ` Chen, Kenneth W [this message]
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=200503291902.j2TJ2Dg00724@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®