From: mwilck@suse.com
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
Hannes Reinecke <hare@suse.de>, Martin Wilck <mwilck@suse.com>
Subject: [PATCH v4 0/6] scsi: fixes for targets with many LUNs, and scsi_target_block rework
Date: Mon, 12 Jun 2023 17:03:03 +0200 [thread overview]
Message-ID: <20230612150309.18103-1-mwilck@suse.com> (raw)
From: Martin Wilck <mwilck@suse.com>
This patch series addresses some issues we saw in a test setup
with a large number of SCSI LUNs. The first two patches simply
increase the number of available sg and bsg devices. 3-5 fix
a large delay we encountered between blocking a Fibre Channel
remote port and the dev_loss_tmo. 6 renames scsi_target_block()
to scsi_block_targets(), and makes additional changes to this API,
as suggested in the review of the v2 series.
Changes v3 -> v4:
- skipped 4/8: keep state_mutex held while quiescing queue (Bart van Assche),
added a comment in 4/6 to explain the rationale
- renamed scsi_target_block() to scsi_block_targets() (Christoph Hellwig), and
merged the previous patches 7/8 and 8/8 modifying this API into 6/6.
- rebased to latest mkp/queue branch
Changes v2 -> v3:
- Split previous 3/3 into 4 separate patches as suggested by
Christoph Hellwig.
- Added 7/8 and 8/8, as suggested by Christoph and Bart van Assche.
- Added s-o-b and reviewed-by tags.
Changes v1 -> v2:
- call blk_mq_wait_quiesce_done() from scsi_target_block() to
cover the case where BLK_MQ_F_BLOCKING is set (Bart van Assche)
Hannes Reinecke (2):
bsg: increase number of devices
scsi: sg: increase number of devices
Martin Wilck (4):
scsi: merge scsi_internal_device_block() and device_block()
scsi: don't wait for quiesce in scsi_stop_queue()
scsi: don't wait for quiesce in scsi_device_block()
scsi: replace scsi_target_block() by scsi_block_targets()
block/bsg.c | 2 +-
drivers/scsi/scsi_lib.c | 76 ++++++++++++++---------------
drivers/scsi/scsi_transport_fc.c | 2 +-
drivers/scsi/scsi_transport_iscsi.c | 3 +-
drivers/scsi/scsi_transport_srp.c | 6 +--
drivers/scsi/sg.c | 2 +-
drivers/scsi/snic/snic_disc.c | 2 +-
include/scsi/scsi_device.h | 2 +-
8 files changed, 46 insertions(+), 49 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-12 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 15:03 mwilck [this message]
2023-06-12 15:03 ` [PATCH v4 1/6] bsg: increase number of devices mwilck
2023-06-12 15:03 ` [PATCH v4 2/6] scsi: sg: " mwilck
2023-06-12 15:03 ` [PATCH v4 3/6] scsi: merge scsi_internal_device_block() and device_block() mwilck
2023-06-12 15:35 ` Bart Van Assche
2023-06-12 16:06 ` Martin Wilck
2023-06-12 15:03 ` [PATCH v4 4/6] scsi: don't wait for quiesce in scsi_stop_queue() mwilck
2023-06-12 15:40 ` Bart Van Assche
2023-06-12 15:03 ` [PATCH v4 5/6] scsi: don't wait for quiesce in scsi_device_block() mwilck
2023-06-12 15:03 ` [PATCH v4 6/6] scsi: replace scsi_target_block() by scsi_block_targets() mwilck
2023-06-12 15:49 ` Bart Van Assche
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=20230612150309.18103-1-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--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