From: James Bottomley <James.Bottomley@steeleye.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: 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 10:52:51 -0500 [thread overview]
Message-ID: <200301151552.h0FFqp402401@localhost.localdomain> (raw)
In-Reply-To: Message from "Martin Peschke3" <MPESCHKE@de.ibm.com> of "Wed, 15 Jan 2003 16:35:35 +0100." <OFD72246CF.E2385102-ONC1256CAF.0050D1E1@de.ibm.com>
MPESCHKE@de.ibm.com said:
> If anybody on the list has objections against 64 bit LUNs, it is now
> time to speak out.
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.
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).
While we're in the middle of pulling these fields out of Scsi_Cmnd is a good
point to start on this.
Most of the mid-layer uses Scsi_Device and doesn't care what the values are,
the only piece that will need careful thought is the legacy scanning code.
James
next prev parent reply other threads:[~2003-01-15 15:52 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 [this message]
2003-01-15 17:12 ` Mike Anderson
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=200301151552.h0FFqp402401@localhost.localdomain \
--to=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