From: Luben Tuikov <luben@splentec.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Martin Peschke3 <MPESCHKE@de.ibm.com>,
patmans@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI Core patches
Date: Wed, 15 Jan 2003 12:40:13 -0500 [thread overview]
Message-ID: <3E259CFD.8010305@splentec.com> (raw)
In-Reply-To: 20030115171233.GC1910@beaverton.ibm.com
Mike Anderson wrote:
>
> object. A transport specific lib could contain common routines
> which the LLDD could use or provide there own ops.
Uuuuh, I think that this will be too bulky for its purpose.
All we want is to present the target port/device name/identifier,
aka ``target ID'', and the LUN. Both of those are fairly simple
and trivial to implement.
I do not think that the LLDD should be burdened with more callbacks
for this. This makes it too messy and too complicated for no reason.
As was suggested before by someone, and I concurred, SCSI Core can
do translations for old and dumb drivers, but newer LLDD, would
accept an actual LUN (64 bits), and an actual target identifier.
I.e. the LLDD shouldn't know what hit them.
Latest news is that SPI is completely going away from SPC-3 and SAM-3
which would make it more worthwhile to get this going.
--
Luben
next prev parent reply other threads:[~2003-01-15 17:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 15:35 [PATCH] SCSI Core patches Martin Peschke3
2003-01-15 15:52 ` James Bottomley
2003-01-15 17:12 ` Mike Anderson
2003-01-15 17:40 ` Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 21:29 Martin Peschke3
2003-01-14 22:16 ` Patrick Mansfield
2003-01-14 20:37 Martin Peschke3
2003-01-14 21:27 ` Patrick Mansfield
2003-01-14 20:01 Martin Peschke3
2003-01-14 20:17 ` Patrick Mansfield
2003-01-14 16:19 Martin Peschke3
2003-01-14 16:51 ` Tony Battersby
2003-01-14 18:56 ` Patrick Mansfield
2003-01-07 13:56 Luben Tuikov
2003-01-07 18:21 ` Patrick Mansfield
2003-01-07 19:23 ` Luben Tuikov
2003-01-07 20:33 ` Patrick Mansfield
2003-01-07 22:14 ` Luben Tuikov
2003-01-08 1:36 ` Patrick Mansfield
2003-01-08 5:13 ` Luben Tuikov
2003-01-11 18:12 ` Christoph Hellwig
2003-01-13 20:33 ` Patrick Mansfield
2003-01-13 21:30 ` Luben Tuikov
2003-01-14 18:49 ` Patrick Mansfield
2003-01-14 19:52 ` Luben Tuikov
2003-01-07 19:44 ` Doug Ledford
2003-01-07 22:53 ` Patrick Mansfield
2003-01-08 17:33 ` Luben Tuikov
2003-01-08 21:13 ` Mike Anderson
2003-01-10 12:35 ` Andre Hedrick
2003-01-10 17:06 ` James Bottomley
2003-01-10 19:23 ` Luben Tuikov
2003-01-10 20:05 ` 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=3E259CFD.8010305@splentec.com \
--to=luben@splentec.com \
--cc=James.Bottomley@steeleye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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