linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] add device_configure to the transport classes
Date: 05 Oct 2004 12:18:38 -0500	[thread overview]
Message-ID: <1096996724.2064.56.camel@mulgrave> (raw)
In-Reply-To: <OF2154D688.D97183DA-ONC1256F24.005BD3E3-C1256F24.005EE95C@de.ibm.com>

On Tue, 2004-10-05 at 12:10, Martin Peschke3 wrote:
> now that there is more and more stuff handed over to transport classes,
> would it be feasible to put LUN there as well, as its form appears to be
> transport specific as well? (e.g. 64 bit for FC while other transports
> may be unable to convey 64 bit LUNs)

Well, I'm not sure about that, primarily because the LUN specifications
in the standards aren't transport specific.

> I see that this particular patch is not exactly what was needed to achieve
> this, because at the time of the evaluation INQUIRY data the LUN has
> already been adapted to the way LUNs are stored in scsi_device.
> 
> I am also not sure yet how this approach would go with REPORT_LUNS,
> which returns 64 bit LUNs for all transports. But for everybody interested
> in 64 bit LUNs, it would certainly clean things up.

Yes, that's another reason to make it transport specific.  Even SPI code
has to understand 64 bit LUN returns.

James



  reply	other threads:[~2004-10-05 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 17:10 [PATCH] add device_configure to the transport classes Martin Peschke3
2004-10-05 17:18 ` James Bottomley [this message]
2004-10-06  4:59   ` Douglas Gilbert
2004-10-06 15:22     ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06 16:52 Martin Peschke3
2004-10-06 16:29 Martin Peschke3
2004-10-06 21:48 ` Luben Tuikov
2004-10-05 16:11 James Bottomley

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=1096996724.2064.56.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=MPESCHKE@de.ibm.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).