All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Bob Liu <bob.liu@oracle.com>, <linux-kernel@vger.kernel.org>
Cc: <hch@infradead.org>, <xen-devel@lists.xenproject.org>,
	<avanzini.arianna@gmail.com>, <david.vrabel@citrix.com>,
	<konrad.wilk@oracle.com>, <marcus.granado@citrix.com>,
	<roger.pau@citrix.com>
Subject: Re: [PATCH v2] xen/blkfront: convert to blk-mq APIs
Date: Sat, 11 Jul 2015 12:14:58 -0600	[thread overview]
Message-ID: <55A15D22.4020709@fb.com> (raw)
In-Reply-To: <1436621418-6742-1-git-send-email-bob.liu@oracle.com>

On 07/11/2015 07:30 AM, Bob Liu wrote:
> Note: This patch is based on original work of Arianna's internship for
> GNOME's Outreach Program for Women.

Great to see this finally get prepped to go in!

> Only one hardware queue is used now, so there is no performance change.

I would hope that the blk-mq path, even with one queue, is a perf win 
over the old interface. So I'm not sure that is correct. But the bigger 
win will be with more queues, of course.

> The legacy non-mq code is deleted completely which is the same as other
> drivers like virtio, mtip, and nvme.
>
> Also dropped one unnecessary holding of info->io_lock when calling
> blk_mq_stop_hw_queues().
>
> Changes in v2:
>   - Reorganized blk_mq_queue_rq()
>   - Restored most io_locks in place

Looks good to me. The most common error case is the busy-out not 
stopping queues, or not restarting them at completion. But that all 
looks fine.

I would, however, rename blk_mq_queue_rq(). It sounds like a core 
function. blkif_queue_rq() would be more appropriate.

> Signed-off-by: Arianna Avanzini <avanzini.arianna@gmail.com>
> Signed-off-by: Bob Liu <bob.liu@oracle.com>

Acked-by: Jens Axboe <axboe@fb.com>


-- 
Jens Axboe


  reply	other threads:[~2015-07-11 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 13:30 [PATCH v2] xen/blkfront: convert to blk-mq APIs Bob Liu
2015-07-11 18:14 ` Jens Axboe [this message]
2015-07-12  2:00   ` Bob Liu
2015-07-12  2:00   ` Bob Liu
2015-07-11 18:14 ` Jens Axboe
2015-07-13  6:36 ` Christoph Hellwig
2015-07-13  6:36 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2015-07-11 13:30 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=55A15D22.4020709@fb.com \
    --to=axboe@fb.com \
    --cc=avanzini.arianna@gmail.com \
    --cc=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hch@infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus.granado@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.