From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: dougg@torque.net, James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] add device_configure to the transport classes
Date: Wed, 06 Oct 2004 17:48:56 -0400 [thread overview]
Message-ID: <41646848.6080108@adaptec.com> (raw)
In-Reply-To: <OF4B71AD6D.2ACA3A91-ONC1256F25.00518CAF-C1256F25.005B33E2@de.ibm.com>
Martin Peschke3 wrote:
>
>
>
>
> > That is right, 64 bit LUNs were mandated in SAM-2
> > (standardized in 2003) and SAM-3 (soon to become a standard).
>
> So, do you know how to read table A.2? (Yes, it's only "informative",
> and therewith not normative)
>
> > When SCSI devices start using advanced LUN features like
> > "well known logical units" (SPC-3 rev 21 section 8)
> > we are really going to start hurting.
>
> I see. The bone of contention from my perspective has been that LLDDs
> are currently required to guess in which way the mid-layer has compressed
> a LUN, and the resulting question: "Which LUN addressing modes does
> your LLDD support?" Ouch!
I remember we talked about 64 bit LUNs 2 years ago on linux-scsi.
I think the LUN (structure) should be opaque to SCSI Core.
So in effect, user applications and LLDDs would interpret it,
but SCSI Core would simply pass it back and forth.
Luben
next prev parent reply other threads:[~2004-10-06 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:29 [PATCH] add device_configure to the transport classes Martin Peschke3
2004-10-06 21:48 ` Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 16:52 Martin Peschke3
2004-10-05 17:10 Martin Peschke3
2004-10-05 17:18 ` James Bottomley
2004-10-06 4:59 ` Douglas Gilbert
2004-10-06 15:22 ` Matthew Wilcox
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=41646848.6080108@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=dougg@torque.net \
--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).