From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Martin Peschke3 <MPESCHKE@de.ibm.com>,
patmans@us.ibm.com, Luben Tuikov <luben@splentec.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI Core patches
Date: Wed, 15 Jan 2003 09:12:33 -0800 [thread overview]
Message-ID: <20030115171233.GC1910@beaverton.ibm.com> (raw)
In-Reply-To: <200301151552.h0FFqp402401@localhost.localdomain>
James Bottomley [James.Bottomley@steeleye.com] wrote:
> I don't have any objections, but I do have a suggestion:
>
> It would be nice to be able to use opaque quantites for target and LUN so that
> the FC devices don't have to do this mapping dance between targed and internal
> name. i.e. if a FC driver wants to use the WWN or port for the target there
> should be nothing preventing it.
>
I believe back in this thread I was trying to say this with my nexus
object, but maybe poorly.
Dynix/ptx had a similar model with its unit numbers. Every node in
the config tree had one but only the object knew how to decode it. It
was just passed around as part of the config object.
> All that really matters is that the target and LUN can be rendered to
> and from a string (for printing out and for accepting from
> add/remove-single-device).
The kobjects are close to what your are talking about (see the
kobject.txt doc in the kernel). The have a few entries that we might
not need, but the do not need to be exported to sysfs. They carry a
kobj_type pointer that provides objs to show or store the values in the
object. A transport specific lib could contain common routines
which the LLDD could use or provide there own ops.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-01-15 17:12 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 [this message]
2003-01-15 17:40 ` Luben Tuikov
-- 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=20030115171233.GC1910@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben@splentec.com \
--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