linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Liu <bob.liu@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xen.org, david.vrabel@citrix.com,
	linux-kernel@vger.kernel.org, konrad.wilk@oracle.com,
	felipe.franciosi@citrix.com, axboe@fb.com, hch@infradead.org,
	avanzini.arianna@gmail.com, rafal.mielniczuk@citrix.com,
	boris.ostrovsky@oracle.com, jonathan.davies@citrix.com
Subject: Re: [PATCH v3 5/9] xen/blkfront: convert per device io_lock to per ring ring_lock
Date: Wed, 07 Oct 2015 18:34:06 +0800	[thread overview]
Message-ID: <5614F51E.1020404@oracle.com> (raw)
In-Reply-To: <56128587.7000804@citrix.com>


On 10/05/2015 10:13 PM, Roger Pau Monné wrote:
> El 05/09/15 a les 14.39, Bob Liu ha escrit:
>> The per device io_lock became a coarser grained lock after multi-queues/rings
>> was introduced, this patch converts it to a fine-grained per ring lock.
>>
>> NOTE: The per dev_info structure was no more protected by any lock.
> 
> I would rewrite this as:
> 
> Note that the per-device blkfront_dev_info structure is no longer
> protected by any lock.
> 

Will update.

>>
>> Signed-off-by: Bob Liu <bob.liu@oracle.com>
>> ---
>>  drivers/block/xen-blkfront.c |   44 +++++++++++++++++++-----------------------
>>  1 file changed, 20 insertions(+), 24 deletions(-)
>>
>> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
>> index bf45c99..1cae76b 100644
>> --- a/drivers/block/xen-blkfront.c
>> +++ b/drivers/block/xen-blkfront.c
>> @@ -123,6 +123,7 @@ MODULE_PARM_DESC(max_ring_page_order, "Maximum order of pages to be used for the
>>  struct blkfront_ring_info
>>  {
>>  	struct blkif_front_ring ring;
>> +	spinlock_t ring_lock;
>>  	unsigned int ring_ref[XENBUS_MAX_RING_PAGES];
>>  	unsigned int evtchn, irq;
>>  	struct work_struct work;
>> @@ -141,7 +142,6 @@ struct blkfront_ring_info
>>   * putting all kinds of interesting stuff here :-)
>>   */
>>  struct blkfront_dev_info {
>> -	spinlock_t io_lock;
>>  	struct mutex mutex;
>>  	struct xenbus_device *xbdev;
>>  	struct gendisk *gd;
>> @@ -637,29 +637,28 @@ static int blkif_queue_rq(struct blk_mq_hw_ctx *hctx,
>>  			   const struct blk_mq_queue_data *qd)
>>  {
>>  	struct blkfront_ring_info *rinfo = (struct blkfront_ring_info *)hctx->driver_data;
>> -	struct blkfront_dev_info *dinfo = rinfo->dinfo;
>>  
>>  	blk_mq_start_request(qd->rq);
>> -	spin_lock_irq(&dinfo->io_lock);
>> +	spin_lock_irq(&rinfo->ring_lock);
>>  	if (RING_FULL(&rinfo->ring))
>>  		goto out_busy;
>>  
>> -	if (blkif_request_flush_invalid(qd->rq, dinfo))
>> +	if (blkif_request_flush_invalid(qd->rq, rinfo->dinfo))
>>  		goto out_err;
>>  
>>  	if (blkif_queue_request(qd->rq, rinfo))
>>  		goto out_busy;
>>  
>>  	flush_requests(rinfo);
>> -	spin_unlock_irq(&dinfo->io_lock);
>> +	spin_unlock_irq(&rinfo->ring_lock);
>>  	return BLK_MQ_RQ_QUEUE_OK;
>>  
>>  out_err:
>> -	spin_unlock_irq(&dinfo->io_lock);
>> +	spin_unlock_irq(&rinfo->ring_lock);
>>  	return BLK_MQ_RQ_QUEUE_ERROR;
>>  
>>  out_busy:
>> -	spin_unlock_irq(&dinfo->io_lock);
>> +	spin_unlock_irq(&rinfo->ring_lock);
>>  	blk_mq_stop_hw_queue(hctx);
>>  	return BLK_MQ_RQ_QUEUE_BUSY;
>>  }
>> @@ -961,7 +960,7 @@ static void xlvbd_release_gendisk(struct blkfront_dev_info *dinfo)
>>  	dinfo->gd = NULL;
>>  }
>>  
>> -/* Must be called with io_lock holded */
>> +/* Must be called with ring_lock holded */
>                                     ^ held.
>>  static void kick_pending_request_queues(struct blkfront_ring_info *rinfo)
>>  {
>>  	if (!RING_FULL(&rinfo->ring))
>> @@ -972,10 +971,10 @@ static void blkif_restart_queue(struct work_struct *work)
>>  {
>>  	struct blkfront_ring_info *rinfo = container_of(work, struct blkfront_ring_info, work);
>>  
>> -	spin_lock_irq(&rinfo->dinfo->io_lock);
>> +	spin_lock_irq(&rinfo->ring_lock);
>>  	if (rinfo->dinfo->connected == BLKIF_STATE_CONNECTED)
>>  		kick_pending_request_queues(rinfo);
> 
> This seems wrong, why are you acquiring a per-ring lock in order to
> check a per-device field? IMHO, I think you need to introduce a
> per-device lock or drop the locking around this chunk if it's really not
> needed.
> 

The lock here is to protect kick_pending_request_queues() where we will check RING_FULL().
Will move this lock after the checking of per-device field.

Thanks,
-Bob

>> -	spin_unlock_irq(&rinfo->dinfo->io_lock);
>> +	spin_unlock_irq(&rinfo->ring_lock);
>>  }
>>  

  reply	other threads:[~2015-10-07 10:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05 12:39 [PATCH v3 0/9] xen-block: support multi hardware-queues/rings Bob Liu
2015-09-05 12:39 ` [PATCH v3 1/9] xen-blkfront: convert to blk-mq APIs Bob Liu
2015-09-23 20:31   ` Konrad Rzeszutek Wilk
2015-09-23 21:12     ` Konrad Rzeszutek Wilk
2015-09-05 12:39 ` [PATCH v3 2/9] xen-block: add document for mutli hardware queues/rings Bob Liu
2015-09-23 20:32   ` Konrad Rzeszutek Wilk
2015-10-02 16:04   ` Roger Pau Monné
2015-10-02 16:12     ` [Xen-devel] " Wei Liu
2015-10-02 16:22       ` Roger Pau Monné
2015-10-02 23:55         ` Bob Liu
2015-09-05 12:39 ` [PATCH v3 3/9] xen/blkfront: separate per ring information out of device info Bob Liu
2015-10-02 17:02   ` Roger Pau Monné
2015-10-03  0:34     ` Bob Liu
2015-10-05 15:17       ` Roger Pau Monné
2015-10-10  8:30     ` Bob Liu
2015-10-19  9:42       ` Roger Pau Monné
2015-09-05 12:39 ` [PATCH v3 4/9] xen/blkfront: pseudo support for multi hardware queues/rings Bob Liu
2015-10-05 10:52   ` Roger Pau Monné
2015-10-07 10:28     ` Bob Liu
2015-09-05 12:39 ` [PATCH v3 5/9] xen/blkfront: convert per device io_lock to per ring ring_lock Bob Liu
2015-10-05 14:13   ` Roger Pau Monné
2015-10-07 10:34     ` Bob Liu [this message]
2015-09-05 12:39 ` [PATCH v3 6/9] xen/blkfront: negotiate the number of hw queues/rings with backend Bob Liu
2015-10-05 14:40   ` Roger Pau Monné
2015-10-07 10:39     ` Bob Liu
2015-10-07 11:46       ` Roger Pau Monné
2015-10-07 12:19         ` Bob Liu
2015-09-05 12:39 ` [PATCH v3 7/9] xen/blkback: separate ring information out of struct xen_blkif Bob Liu
2015-10-05 14:55   ` Roger Pau Monné
2015-10-07 10:41     ` Bob Liu
2015-10-10  4:08     ` Bob Liu
2015-10-19  9:36       ` Roger Pau Monné
2015-10-19 10:03         ` Bob Liu
2015-10-05 14:55   ` Roger Pau Monné
2015-09-05 12:39 ` [PATCH v3 8/9] xen/blkback: pseudo support for multi hardware queues/rings Bob Liu
2015-10-05 15:08   ` Roger Pau Monné
2015-10-07 10:50     ` Bob Liu
2015-10-07 11:49       ` Roger Pau Monné
2015-09-05 12:39 ` [PATCH v3 9/9] xen/blkback: get number of hardware queues/rings from blkfront Bob Liu
2015-10-05 15:15   ` Roger Pau Monné
2015-10-07 10:54     ` Bob Liu
2015-10-02  9:57 ` [PATCH v3 0/9] xen-block: support multi hardware-queues/rings Rafal Mielniczuk

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=5614F51E.1020404@oracle.com \
    --to=bob.liu@oracle.com \
    --cc=avanzini.arianna@gmail.com \
    --cc=axboe@fb.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=felipe.franciosi@citrix.com \
    --cc=hch@infradead.org \
    --cc=jonathan.davies@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal.mielniczuk@citrix.com \
    --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;
as well as URLs for NNTP newsgroup(s).