From: Lee Duncan <lduncan@suse.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Hannes Reinecke <hare@suse.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCHv4 1/1] SCSI: hosts: update to use ida_simple for host_no management
Date: Wed, 14 Oct 2015 11:34:00 -0700 [thread overview]
Message-ID: <561EA018.7020700@suse.com> (raw)
In-Reply-To: <1444830904.2220.28.camel@HansenPartnership.com>
On 10/14/2015 06:55 AM, James Bottomley wrote:
> On Wed, 2015-10-07 at 16:51 -0700, Lee Duncan wrote:
>> Update the SCSI hosts module to use the ida_simple*() routines
>> to manage its host_no index instead of an ATOMIC integer. This
>> means that the SCSI host number will now be reclaimable.
>
> OK, but why would we want to do this? We do it for sd because our minor
> space for the device nodes is very constrained, so packing is essential.
> For HBAs, there's no device space density to worry about, they're
> largely statically allocated at boot time and not reusing the numbers
> allows easy extraction of hotplug items for the logs (quite useful for
> USB) because each separate hotplug has a separate and monotonically
> increasing host number.
>
> James
>
Good question, James. Apologies for not making the need clear.
The iSCSI subsystem uses a host structure for discovery, then throws it
away. So each time it does discovery it gets a new host structure. With
the current approach, that number is ever increasing. It's only a matter
of time until some user with a hundreds of disks and perhaps thousands
of LUNs, that likes to do periodic discovery (think super-computers)
will run out of host numbers. Or, worse yet, get a negative number
number (because the value is signed right now).
And this use case is a real one right now, by the way.
As you can see from the patch, it's a small amount of code to ensure
that the host number management is handled more cleanly.
--
Lee Duncan
next prev parent reply other threads:[~2015-10-14 18:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 23:51 [PATCHv4 0/1] Update SCSI hosts to use ida for host number mgmt Lee Duncan
2015-10-07 23:51 ` [PATCHv4 1/1] SCSI: hosts: update to use ida_simple for host_no management Lee Duncan
2015-10-14 12:22 ` Johannes Thumshirn
2015-10-14 13:55 ` James Bottomley
2015-10-14 18:34 ` Lee Duncan [this message]
2015-10-14 18:53 ` James Bottomley
2015-10-14 21:21 ` Lee Duncan
2015-10-15 5:52 ` Hannes Reinecke
2015-10-16 20:03 ` Lee Duncan
2015-10-16 20:03 ` Lee Duncan
2015-10-16 20:14 ` Greg KH
2015-10-16 20:14 ` Greg KH
2015-11-12 16:31 ` Lee Duncan
2015-11-13 21:54 ` Martin K. Petersen
2015-11-16 12:10 ` Hannes Reinecke
2015-11-16 21:47 ` Lee Duncan
2015-11-17 23:20 ` Martin K. Petersen
2015-12-10 21:48 ` Lee Duncan
2015-12-11 15:31 ` Ewan Milne
2015-12-13 19:16 ` Lee Duncan
2015-12-14 15:07 ` Ewan Milne
2015-12-14 15:29 ` Hannes Reinecke
2015-12-14 15:29 ` Hannes Reinecke
2015-12-15 1:55 ` Martin K. Petersen
2015-12-17 19:24 ` Lee Duncan
2016-01-04 19:45 ` Lee Duncan
2016-01-05 23:53 ` Martin K. Petersen
2016-01-20 19:49 ` Lee Duncan
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=561EA018.7020700@suse.com \
--to=lduncan@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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.