From: "Vincent, Pradeep" <pradeepv@amazon.com>
To: Daniel Stodden <daniel.stodden@citrix.com>,
Xen <xen-devel@lists.xensource.com>
Cc: "konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] xen/blkback: Don't let in-flight requests defer pending ones.
Date: Sun, 29 May 2011 01:09:19 -0700 [thread overview]
Message-ID: <CA074810.18A24%pradeepv@amazon.com> (raw)
In-Reply-To: <1306614070-13137-1-git-send-email-daniel.stodden@citrix.com>
Opportunistically avoiding interrupts by checking for I/Os in the flight
doesn't sound like a bad idea. I think the RING_HAS_UNCONSUMED_REQUESTS
call and what follows should be retained in 'make_response'.
Also, should RING_FINAL_CHECK_FOR_REQUESTS be protected by blk_ring_lock ?
- Pradeep Vincent
On 5/28/11 1:21 PM, "Daniel Stodden" <daniel.stodden@citrix.com> wrote:
>Running RING_FINAL_CHECK_FOR_REQUESTS from make_response is a bad
>idea. It means that in-flight I/O is essentially blocking continued
>batches. This essentially kills throughput on frontends which unplug
>(or even just notify) early and rightfully assume addtional requests
>will be picked up on time, not synchronously.
>
>Signed-off-by: Daniel Stodden <daniel.stodden@citrix.com>
>---
> drivers/block/xen-blkback/blkback.c | 36
>++++++++++++++++++----------------
> 1 files changed, 19 insertions(+), 17 deletions(-)
>
>diff --git a/drivers/block/xen-blkback/blkback.c
>b/drivers/block/xen-blkback/blkback.c
>index 9dee545..48ad7fa 100644
>--- a/drivers/block/xen-blkback/blkback.c
>+++ b/drivers/block/xen-blkback/blkback.c
>@@ -451,7 +451,8 @@ static void end_block_io_op(struct bio *bio, int
>error)
> * (which has the sectors we want, number of them, grant references,
>etc),
> * and transmute it to the block API to hand it over to the proper
>block disk.
> */
>-static int do_block_io_op(struct xen_blkif *blkif)
>+static int
>+__do_block_io_op(struct xen_blkif *blkif)
> {
> union blkif_back_rings *blk_rings = &blkif->blk_rings;
> struct blkif_request req;
>@@ -508,6 +509,23 @@ static int do_block_io_op(struct xen_blkif *blkif)
> return more_to_do;
> }
>
>+static int
>+do_block_io_op(blkif_t *blkif)
>+{
>+ blkif_back_rings_t *blk_rings = &blkif->blk_rings;
>+ int more_to_do;
>+
>+ do {
>+ more_to_do = __do_block_io_op(blkif);
>+ if (more_to_do)
>+ break;
>+
>+ RING_FINAL_CHECK_FOR_REQUESTS(&blk_rings->common, more_to_do);
>+ } while (more_to_do);
>+
>+ return more_to_do;
>+}
>+
> /*
> * Transmutation of the 'struct blkif_request' to a proper 'struct bio'
> * and call the 'submit_bio' to pass it to the underlying storage.
>@@ -698,7 +716,6 @@ static void make_response(struct xen_blkif *blkif,
>u64 id,
> struct blkif_response resp;
> unsigned long flags;
> union blkif_back_rings *blk_rings = &blkif->blk_rings;
>- int more_to_do = 0;
> int notify;
>
> resp.id = id;
>@@ -725,22 +742,7 @@ static void make_response(struct xen_blkif *blkif,
>u64 id,
> }
> blk_rings->common.rsp_prod_pvt++;
> RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&blk_rings->common, notify);
>- if (blk_rings->common.rsp_prod_pvt == blk_rings->common.req_cons) {
>- /*
>- * Tail check for pending requests. Allows frontend to avoid
>- * notifications if requests are already in flight (lower
>- * overheads and promotes batching).
>- */
>- RING_FINAL_CHECK_FOR_REQUESTS(&blk_rings->common, more_to_do);
>-
>- } else if (RING_HAS_UNCONSUMED_REQUESTS(&blk_rings->common)) {
>- more_to_do = 1;
>- }
>-
> spin_unlock_irqrestore(&blkif->blk_ring_lock, flags);
>-
>- if (more_to_do)
>- blkif_notify_work(blkif);
> if (notify)
> notify_remote_via_irq(blkif->irq);
> }
>--
>1.7.4.1
>
next prev parent reply other threads:[~2011-05-29 8:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 7:04 [PATCH] blkback: Fix block I/O latency issue Vincent, Pradeep
2011-05-02 8:13 ` Jan Beulich
2011-05-03 1:10 ` Vincent, Pradeep
2011-05-03 14:55 ` Konrad Rzeszutek Wilk
2011-05-03 17:16 ` Vincent, Pradeep
2011-05-03 17:51 ` Daniel Stodden
2011-05-03 23:41 ` Vincent, Pradeep
2011-05-03 17:52 ` Daniel Stodden
2011-05-04 1:54 ` Vincent, Pradeep
2011-05-09 20:24 ` Konrad Rzeszutek Wilk
2011-05-13 0:40 ` Vincent, Pradeep
2011-05-13 2:51 ` Konrad Rzeszutek Wilk
2011-05-16 15:22 ` Konrad Rzeszutek Wilk
2011-05-20 6:12 ` Vincent, Pradeep
2011-05-24 16:02 ` Konrad Rzeszutek Wilk
2011-05-24 22:40 ` Vincent, Pradeep
2011-05-28 20:12 ` [RE-PATCH] " Daniel Stodden
2011-05-28 20:21 ` [PATCH] xen/blkback: Don't let in-flight requests defer pending ones Daniel Stodden
2011-05-29 8:09 ` Vincent, Pradeep [this message]
2011-05-29 11:34 ` Daniel Stodden
2011-06-01 8:02 ` Vincent, Pradeep
2011-06-01 8:24 ` Jan Beulich
2011-06-01 17:49 ` Daniel Stodden
2011-06-01 18:07 ` Daniel Stodden
2011-06-27 14:03 ` Konrad Rzeszutek Wilk
2011-06-27 18:42 ` Daniel Stodden
2011-06-27 19:13 ` Konrad Rzeszutek Wilk
2011-06-28 0:31 ` Daniel Stodden
2011-06-28 13:19 ` Konrad Rzeszutek Wilk
2011-05-31 13:44 ` Fix wrong help message for parameter nestedhvm Dong, Eddie
2011-05-31 16:23 ` Ian Campbell
2011-05-31 16:08 ` [PATCH] xen/blkback: Don't let in-flight requests defer pending ones Konrad Rzeszutek Wilk
2011-05-31 16:30 ` Daniel Stodden
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=CA074810.18A24%pradeepv@amazon.com \
--to=pradeepv@amazon.com \
--cc=daniel.stodden@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).