From: Christoph Hellwig <hch@infradead.org>
To: Bob Liu <bob.liu@oracle.com>
Cc: xen-devel@lists.xen.org, david.vrabel@citrix.com,
linux-kernel@vger.kernel.org, roger.pau@citrix.com,
konrad.wilk@oracle.com, felipe.franciosi@citrix.com,
axboe@fb.com, hch@infradead.org, avanzini.arianna@gmail.com
Subject: Re: [PATCH 03/10] xen/blkfront: reorg info->io_lock after using blk-mq API
Date: Wed, 18 Feb 2015 09:05:52 -0800 [thread overview]
Message-ID: <20150218170552.GC17813@infradead.org> (raw)
In-Reply-To: <1423988345-4005-4-git-send-email-bob.liu@oracle.com>
On Sun, Feb 15, 2015 at 04:18:58PM +0800, Bob Liu wrote:
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index 3589436..5a90a51 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -614,25 +614,28 @@ static int blk_mq_queue_rq(struct blk_mq_hw_ctx *hctx,
> blk_mq_start_request(qd->rq);
> spin_lock_irq(&info->io_lock);
> if (RING_FULL(&info->ring)) {
> + spin_unlock_irq(&info->io_lock);
> blk_mq_stop_hw_queue(hctx);
> ret = BLK_MQ_RQ_QUEUE_BUSY;
> goto out;
> }
>
> if (blkif_request_flush_invalid(qd->rq, info)) {
> + spin_unlock_irq(&info->io_lock);
> ret = BLK_MQ_RQ_QUEUE_ERROR;
> goto out;
> }
>
> if (blkif_queue_request(qd->rq)) {
> + spin_unlock_irq(&info->io_lock);
> blk_mq_stop_hw_queue(hctx);
> ret = BLK_MQ_RQ_QUEUE_BUSY;
> goto out;
> }
>
> flush_requests(info);
> -out:
> spin_unlock_irq(&info->io_lock);
> +out:
> return ret;
> }
I'd rather write the function something like:
spin_lock_irq(&info->io_lock);
if (RING_FULL(&info->ring))
goto out_busy;
if (blkif_request_flush_invalid(qd->rq, info))
goto out_error;
if (blkif_queue_request(qd->rq))
goto out_busy;
flush_requests(info);
spin_unlock_irq(&info->io_lock);
return BLK_MQ_RQ_QUEUE_OK;
out_error:
spin_unlock_irq(&info->io_lock);
return BLK_MQ_RQ_QUEUE_ERROR;
out_busy:
spin_unlock_irq(&info->io_lock);
blk_mq_stop_hw_queue(hctx);
return BLK_MQ_RQ_QUEUE_BUSY;
}
Also this really should be merged into the first patch.
next prev parent reply other threads:[~2015-02-18 17:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 8:18 [RFC PATCH 00/10] Multi-queue support for xen-block driver Bob Liu
2015-02-15 8:18 ` [PATCH 01/10] xen/blkfront: convert to blk-mq API Bob Liu
2015-02-15 8:18 ` [PATCH 02/10] xen/blkfront: drop legacy block layer support Bob Liu
2015-02-18 17:02 ` Christoph Hellwig
2015-02-15 8:18 ` [PATCH 03/10] xen/blkfront: reorg info->io_lock after using blk-mq API Bob Liu
2015-02-18 17:05 ` Christoph Hellwig [this message]
2015-02-19 2:07 ` Bob Liu
2015-02-15 8:18 ` [PATCH 04/10] xen/blkfront: separate ring information to an new struct Bob Liu
2015-02-18 17:28 ` Roger Pau Monné
2015-02-18 17:37 ` Konrad Rzeszutek Wilk
2015-02-18 18:08 ` Felipe Franciosi
2015-02-18 18:29 ` Konrad Rzeszutek Wilk
2015-02-19 2:05 ` Bob Liu
2015-02-19 11:08 ` Roger Pau Monné
2015-02-19 11:14 ` David Vrabel
2015-02-19 12:06 ` Felipe Franciosi
2015-02-19 13:12 ` Roger Pau Monné
2015-02-20 18:59 ` Konrad Rzeszutek Wilk
2015-02-27 12:52 ` Bob Liu
2015-03-04 21:21 ` Konrad Rzeszutek Wilk
2015-03-05 0:47 ` Bob Liu
2015-03-06 10:30 ` Felipe Franciosi
2015-03-17 7:00 ` Bob Liu
2015-03-17 14:52 ` Felipe Franciosi
2015-03-18 0:52 ` Bob Liu
2015-02-15 8:19 ` [PATCH 05/10] xen/blkback: separate ring information out of struct xen_blkif Bob Liu
2015-02-15 8:19 ` [PATCH 06/10] xen/blkfront: pseudo support for multi hardware queues Bob Liu
2015-02-15 8:19 ` [PATCH 07/10] xen/blkback: " Bob Liu
2015-02-19 16:57 ` [Xen-devel] " David Vrabel
2015-02-15 8:19 ` [PATCH 08/10] xen/blkfront: negotiate hardware queue number with backend Bob Liu
2015-02-15 8:19 ` [PATCH 09/10] xen/blkback: get hardware queue number from blkfront Bob Liu
2015-02-15 8:19 ` [PATCH 10/10] xen/blkfront: use work queue to fast blkif interrupt return Bob Liu
2015-02-19 16:51 ` [Xen-devel] " David Vrabel
2015-02-18 17:01 ` [RFC PATCH 00/10] Multi-queue support for xen-block driver Christoph Hellwig
2015-02-18 18:22 ` Felipe Franciosi
2015-02-19 2:04 ` Bob Liu
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=20150218170552.GC17813@infradead.org \
--to=hch@infradead.org \
--cc=avanzini.arianna@gmail.com \
--cc=axboe@fb.com \
--cc=bob.liu@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=felipe.franciosi@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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