From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [SCSI] remove arbitrary SD_MAX_DISKS namespace limit
Date: Mon, 03 Oct 2011 13:29:24 -0500 [thread overview]
Message-ID: <4E89FF04.4040208@oracle.com> (raw)
In-Reply-To: <1317664679.3041.48.camel@dabdike.int.hansenpartnership.com>
On 10/03/2011 12:57 PM, James Bottomley wrote:
> On Mon, 2011-10-03 at 11:47 -0500, Dave Kleikamp wrote:
>> I see no reason to limit the SCSI disk namespace to sdXXX. We test
>> systems with more than 18278 LUNs.
>
> I suppose we kept the old limit for historical reasons, so I've no real
> objection to raising it, except the error messages now need to be beefed
> up. We need one for the ida_get_new() failure and the original
> exhaustion messages needs to move to the sd_format_disk_name() check ...
> that's now what checks we don't go over the possible size in
> DISK_NAME_LEN (I know at 32 it's way beyond INT_MAX ... but just in case
> someone decides to lower it) ... probably it's the same error message
> (but better make it unique for the static checkers).
I'll defer to your judgment on how to fix this. I didn't look at your
git tree, just mainline. Just bumping up SD_MAX_DISKS is sufficient.
Wrapping the calculation in another (( ...) + 1) * 26 should get us
through another decade, I would think. :-) Or any reasonably high
number. INT_MAX?
Thanks,
Shaggy
next prev parent reply other threads:[~2011-10-03 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:47 [PATCH] [SCSI] remove arbitrary SD_MAX_DISKS namespace limit Dave Kleikamp
2011-10-03 17:57 ` James Bottomley
2011-10-03 18:29 ` Dave Kleikamp [this message]
2011-10-19 16:49 ` [PATCH v2] " Dave Kleikamp
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=4E89FF04.4040208@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.