From: Jeremy Linton <jlinton@tributary.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: James Bottomley <jbottomley@parallels.com>,
Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: Allow 64-bit LUNs during report lun scan
Date: Thu, 14 Feb 2013 16:38:23 -0600 [thread overview]
Message-ID: <511D675F.6020009@tributary.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402950D58E9A@G9W0745.americas.hpqcorp.net>
On 2/14/2013 4:04 PM, Elliott, Robert (Server Storage) wrote:
> Like James notes, LUNs should generally be treated as opaque values.
I agree, except there is a max host lun check based on a decoded lun value. Not
really sure why its there other than maybe some of the HBA's have resource
issues with a large number of luns.
> scsilun_to_int() does not appear to be used very much; I see 35 matches in linux-3.7-rc5. Perhaps the callers should be updated to support 64-bit LUNs and decide what to do if they cannot handle larger values.
Which is a perfectly valid fix, but if that is being done, why do any swizzling
in scsilun_to_int()?
next prev parent reply other threads:[~2013-02-14 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:06 [PATCH] scsi: Allow 64-bit LUNs during report lun scan Hannes Reinecke
2013-02-13 19:52 ` Jeremy Linton
2013-02-13 20:21 ` Bart Van Assche
2013-02-14 3:38 ` James Bottomley
2013-02-14 18:02 ` Jeremy Linton
2013-02-14 22:04 ` Elliott, Robert (Server Storage)
2013-02-14 22:38 ` Jeremy Linton [this message]
2013-02-14 22:44 ` Jeremy Linton
2013-02-15 7:26 ` Hannes Reinecke
2013-02-15 7:33 ` Bart Van Assche
2013-02-15 7:15 ` Hannes Reinecke
2013-02-14 3:37 ` James Bottomley
2013-02-14 21:21 ` Jeremy Linton
2013-02-15 16:25 ` Jeremy Linton
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=511D675F.6020009@tributary.com \
--to=jlinton@tributary.com \
--cc=Elliott@hp.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.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.