All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jeremy Linton <jlinton@tributary.com>
Cc: Hannes Reinecke <hare@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>
Subject: Re: [PATCH] scsi: Allow 64-bit LUNs during report lun scan
Date: Wed, 13 Feb 2013 21:21:31 +0100	[thread overview]
Message-ID: <511BF5CB.2030202@acm.org> (raw)
In-Reply-To: <511BEF0B.4020302@tributary.com>

On 02/13/13 20:52, Jeremy Linton wrote:
> On 2/13/2013 9:06 AM, Hannes Reinecke wrote:
>> So add a new flag 'support_64bit_luns' to the scsi host and modify report
>> lun scan to not check for max_luns during scanning if that flag is set.
>> This will get rid of the
>
> 	Along these lines, I don't think the scsilun_to_int() and int_to_scsilun()
> routines are correct for > 2^14  luns. SAM  4.6 defines bits 6,7 of byte zero
> in the LU representation format as the address method. Which when set to 00b
> limits it to 256 luns but the overflow into the bus ID probably works for some
> devices.
>
> 	Those routines should probably select/detect an alternative address method
> for luns > 256.
>
> 	Or am I missing something?

I think the LUN-to-int translation should depend on the LUN addressing 
method supported by the target. SAM-5 defines the following LUN 
addressing methods:
a) peripheral device addressing method;
b) flat space addressing method;
c) logical unit addressing method,
d) extended logical unit addressing method;
e) long extended logical unit addressing method.

scsilun_to_int() does the translation correctly for some of these 
addressing methods but not for all of them.

Bart.


  reply	other threads:[~2013-02-13 20:21 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 [this message]
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
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=511BF5CB.2030202@acm.org \
    --to=bvanassche@acm.org \
    --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 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.