From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bob Liu <bob.liu@oracle.com>
Cc: linux-kernel@vger.kernel.org, axboe@fb.com, hch@infradead.org,
xen-devel@lists.xenproject.org, avanzini.arianna@gmail.com,
david.vrabel@citrix.com, marcus.granado@citrix.com,
roger.pau@citrix.com
Subject: Re: [RESEND PATCH] xen/blkfront: convert to blk-mq APIs
Date: Sat, 11 Jul 2015 07:17:18 -0400 [thread overview]
Message-ID: <DF6E8136-CA99-476D-8444-71085D189F8F@oracle.com> (raw)
In-Reply-To: <55A0D162.1020002@oracle.com>
On July 11, 2015 4:18:42 AM EDT, Bob Liu <bob.liu@oracle.com> wrote:
>
>On 07/11/2015 03:57 AM, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jul 06, 2015 at 05:56:48PM +0800, Bob Liu wrote:
>>> From: Arianna Avanzini <avanzini.arianna@gmail.com>
>>>
>>> This patch converts xen-blkfront driver to use the block multiqueue
>APIs.
>>> Only one hardware queue is used now, so there is no performance
>change.
>>>
>>> The legacy non-mq code was deleted completely which is the same as
>other drivers
>>> like virtio, mtip, and nvme.
>>>
>>> Also dropped unnecessary holding of info->io_lock when calling into
>blk-mq APIs.
>>
>> Yeey!
>>
>> Two points:
>>
>> - The io_lock is now used to guard against concurrent access to the
>ring.
>> We should rename it to 'ring_lock'.
>>
>
>Sure.
>
>> - The kick_pending_request_queues should have an extra argument -
>'bool locked'.
>> This is so that you don't drop and immediately grab the lock from
>the blkif_interrupt.
>>
>
>Then where to drop the lock?
The 'locked' parameter can be used to tell the function to not take the lock.
But it would drop the lock in both cases.
>
>In kick_pending_request_queues(), the lock have to be dropped before
>calling blk_mq_start_stopped_hw_queues().
>
> static void kick_pending_request_queues(struct blkfront_info *info)
> {
>+ unsigned long flags;
>+
>+ spin_lock_irqsave(&info->io_lock, flags);
> if (!RING_FULL(&info->ring)) {
>- /* Re-enable calldowns. */
>- blk_start_queue(info->rq);
>- /* Kick things off immediately. */
>- do_blkif_request(info->rq);
>+ spin_unlock_irqrestore(&info->io_lock, flags);
>+ blk_mq_start_stopped_hw_queues(info->rq, true);
>+ return;
> }
>
>> See:
>>
>>> @@ -1243,9 +1243,8 @@ static irqreturn_t blkif_interrupt(int irq,
>void *dev_id)
>>> } else
>>> info->ring.sring->rsp_event = i + 1;
>>>
>>> - kick_pending_request_queues(info);
>>> -
>>> spin_unlock_irqrestore(&info->io_lock, flags);
>>> + kick_pending_request_queues(info);
>>>
>>> return IRQ_HANDLED;
>>> }
>>
>> Otherwise Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>
next prev parent reply other threads:[~2015-07-11 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 9:56 Bob Liu
2015-07-10 19:57 ` Konrad Rzeszutek Wilk
2015-07-11 8:18 ` Bob Liu
2015-07-11 11:17 ` Konrad Rzeszutek Wilk [this message]
2015-07-11 11:23 ` Christoph Hellwig
2015-07-11 11:54 ` Konrad Rzeszutek Wilk
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=DF6E8136-CA99-476D-8444-71085D189F8F@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=avanzini.arianna@gmail.com \
--cc=axboe@fb.com \
--cc=bob.liu@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hch@infradead.org \
--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 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®