From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/2] struct scsi_lun preparation
Date: Mon, 11 Sep 2006 15:55:40 -0400 [thread overview]
Message-ID: <4505BF3C.8070806@garzik.org> (raw)
In-Reply-To: <1157995742.3470.10.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-09-11 at 10:34 -0400, Jeff Garzik wrote:
>> A long-term, low priority project of mine is to increasingly isolate
>> HCIL addressing, making it easier to directly support FC/SAS-style
>> addressing without hacks and HCIL emulation.
>
> I'm not sure we want to embed an actual struct scsi_lun into the whole
> of the scsi subsystem. At the moment, given that no-one's actually
> managed to find any device that goes beyond two levels, the current u32
> for lun is perfectly fine. If we're eventually forced beyond two
> levels, we can consider the transition (although going to u64 does look
> tempting).
>
> A pretty print for the current u32 would be very useful though for
> transports dealing with non single level luns (or address methods other
> than zero).
A better subject line would have been "HCIL isolation" I suppose. I
would like to see increased usage of the accessors already present in
include/scsi/scsi_device.h, which would ease the transition from
hardcoded HCIL struct members to a more flexible addressing method.
Though, FWIW, for LUNs I would certainly like to see u64 rather than
u32.....
Jeff
next prev parent reply other threads:[~2006-09-11 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 14:34 [PATCH 0/2] struct scsi_lun preparation Jeff Garzik
2006-09-11 14:34 ` [PATCH 1/2] " Jeff Garzik
2006-09-11 14:35 ` [PATCH 2/2] " Jeff Garzik
2006-09-11 14:42 ` [PATCH 1/2] " Matthew Wilcox
2006-09-11 17:29 ` [PATCH 0/2] " James Bottomley
2006-09-11 19:55 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-11 20:43 Moore, Eric
2006-09-11 21:41 ` Jeff Garzik
2006-09-12 19:33 ` Luben Tuikov
2006-09-13 4:27 ` Douglas Gilbert
2006-09-12 19:21 ` Luben Tuikov
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=4505BF3C.8070806@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.