From: Bart Van Assche <bvanassche@acm.org>
To: Jeremy Linton <jlinton@tributary.com>
Cc: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
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: Fri, 15 Feb 2013 08:33:21 +0100 [thread overview]
Message-ID: <511DE4C1.5000000@acm.org> (raw)
In-Reply-To: <511D68CA.6050203@tributary.com>
On 02/14/13 23:44, Jeremy Linton wrote:
> On 2/14/2013 4:04 PM, Elliott, Robert (Server Storage) wrote:
>> Like James notes, LUNs should generally be treated as opaque values.
>
> Maybe another issue to consider is how they are being displayed in userland.
> A device with two luns using one of the alternative lun addressing methods is
> going to get some pretty strange looking lun numbers showing up in userspace
> if they aren't decoded properly.
One example of this is the ibmvscsi protocol. Since the ibmvscsi target
driver uses the LUN addressing method its LUNs show up with LUN numbers
256 512 768 ... at a Linux SCSI initiator.
Bart.
next prev parent reply other threads:[~2013-02-15 7:33 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
2013-02-14 22:44 ` Jeremy Linton
2013-02-15 7:26 ` Hannes Reinecke
2013-02-15 7:33 ` Bart Van Assche [this message]
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=511DE4C1.5000000@acm.org \
--to=bvanassche@acm.org \
--cc=Elliott@hp.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=jlinton@tributary.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).