public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
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 <Bart.VanAssche@sandisk.com>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
	Hannes Reinecke <hare@suse.de>,
	Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 1/8] bsg: increase number of devices
Date: Wed,  7 Jun 2023 20:22:42 +0200	[thread overview]
Message-ID: <20230607182249.22623-2-mwilck@suse.com> (raw)
In-Reply-To: <20230607182249.22623-1-mwilck@suse.com>

From: Hannes Reinecke <hare@suse.de>

Larger setups may need to allocate more than 32k bsg devices, so
increase the number of devices to the full range of minor device
numbers.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Martin Wilck <mwilck@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
---
 block/bsg.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/block/bsg.c b/block/bsg.c
index 7eca43f33d7f..c53f24243bf2 100644
--- a/block/bsg.c
+++ b/block/bsg.c
@@ -36,7 +36,7 @@ static inline struct bsg_device *to_bsg_device(struct inode *inode)
 }
 
 #define BSG_DEFAULT_CMDS	64
-#define BSG_MAX_DEVS		32768
+#define BSG_MAX_DEVS		(1 << MINORBITS)
 
 static DEFINE_IDA(bsg_minor_ida);
 static struct class *bsg_class;
-- 
2.40.1


  reply	other threads:[~2023-06-07 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 18:22 [PATCH v3 0/8] scsi: fixes for targets with many LUNs, and scsi_target_block rework mwilck
2023-06-07 18:22 ` mwilck [this message]
2023-06-07 18:22 ` [PATCH v3 2/8] scsi: sg: increase number of devices mwilck
2023-06-07 18:22 ` [PATCH v3 3/8] scsi: merge scsi_internal_device_block() and device_block() mwilck
2023-06-07 19:10   ` Bart Van Assche
2023-06-08  5:42   ` Christoph Hellwig
2023-06-07 18:22 ` [PATCH v3 4/8] scsi: call scsi_stop_queue() without state_mutex held mwilck
2023-06-07 19:16   ` Bart Van Assche
2023-06-07 19:37     ` Martin Wilck
2023-06-07 20:07       ` Martin Wilck
2023-06-08  5:44         ` Christoph Hellwig
2023-06-08 14:12           ` Bart Van Assche
2023-06-08 18:54             ` Mike Christie
2023-06-12 11:15               ` Martin Wilck
2023-06-12 13:41                 ` Bart Van Assche
2023-06-07 18:22 ` [PATCH v3 5/8] scsi: don't wait for quiesce in scsi_stop_queue() mwilck
2023-06-08  5:46   ` Christoph Hellwig
2023-06-07 18:22 ` [PATCH v3 6/8] scsi: don't wait for quiesce in scsi_device_block() mwilck
2023-06-07 18:22 ` [PATCH v3 7/8] scsi: have scsi_target_block() expect a scsi_target parent argument mwilck
2023-06-08  5:48   ` Christoph Hellwig
2023-06-07 18:22 ` [PATCH v3 8/8] scsi: add Scsi_Host argument to scsi_target_block() mwilck

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=20230607182249.22623-2-mwilck@suse.com \
    --to=mwilck@suse.com \
    --cc=Bart.VanAssche@sandisk.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