Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Steffen Maier <maier@linux.ibm.com>
To: Ming Lei <ming.lei@redhat.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	Christoph Hellwig <hch@lst.de>, Dexuan Cui <decui@microsoft.com>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] scsi: avoid to run synchronize_rcu for each device in scsi_host_block
Date: Wed, 22 Apr 2020 18:19:48 +0200	[thread overview]
Message-ID: <540025fc-366b-e895-f4cd-b7ac3fdffbe0@linux.ibm.com> (raw)
In-Reply-To: <20200422101433.321581-1-ming.lei@redhat.com>

On 4/22/20 12:14 PM, Ming Lei wrote:
> scsi_host_block() calls scsi_internal_device_block() for each
> scsi_device, and scsi_internal_device_block() calls
> blk_mq_quiesce_queue() for each LUN. However synchronize_rcu is
> run from blk_mq_quiesce_queue().
> 
> This way may become unnecessary slow in case of lots of LUNs.
> 
> So use scsi_internal_device_block() to implement scsi_host_block(),

scsi_internal_device_block()
=?=>
scsi_internal_device_block_nowait()

> and just run once synchronize_rcu() because scsi never supports
> tagset of BLK_MQ_F_BLOCKING.
> 
> Cc: Bart Van Assche <bvanassche@acm.org>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Dexuan Cui <decui@microsoft.com>
> Cc: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
>   drivers/scsi/scsi_lib.c | 13 ++++++++++++-
>   1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index 47835c4b4ee0..089ac92ac6c3 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -2841,11 +2841,22 @@ scsi_host_block(struct Scsi_Host *shost)
>   	struct scsi_device *sdev;
>   	int ret = 0;
>   
> +	/*
> +	 * Call scsi_internal_device_block_nowait then we can avoid to
> +	 * run synchronize_rcu() one time for every LUN.
> +	 */
>   	shost_for_each_device(sdev, shost) {
> -		ret = scsi_internal_device_block(sdev);
> +		mutex_lock(&sdev->state_mutex);
> +		ret = scsi_internal_device_block_nowait(sdev);
> +		mutex_unlock(&sdev->state_mutex);
>   		if (ret)
>   			break;
>   	}
> +
> +	WARN_ON_ONCE(shost->tag_set.flags & BLK_MQ_F_BLOCKING);
> +
> +	if (!ret)
> +		synchronize_rcu();
>   	return ret;
>   }
>   EXPORT_SYMBOL_GPL(scsi_host_block);
> 


-- 
Mit freundlichen Gruessen / Kind regards
Steffen Maier

Linux on IBM Z Development

https://www.ibm.com/privacy/us/en/
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Matthias Hartmann
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294


      parent reply	other threads:[~2020-04-22 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 10:14 [PATCH] scsi: avoid to run synchronize_rcu for each device in scsi_host_block Ming Lei
2020-04-22 15:06 ` Bart Van Assche
2020-04-22 16:19 ` Steffen Maier [this message]

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=540025fc-366b-e895-f4cd-b7ac3fdffbe0@linux.ibm.com \
    --to=maier@linux.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bvanassche@acm.org \
    --cc=decui@microsoft.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.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