From: James Bottomley <James.Bottomley@SteelEye.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: scsi_device::single_lun name change
Date: Tue, 15 Feb 2005 19:53:59 -0600 [thread overview]
Message-ID: <1108518839.5539.93.camel@mulgrave> (raw)
In-Reply-To: <42129A83.7010207@torque.net>
On Wed, 2005-02-16 at 10:57 +1000, Douglas Gilbert wrote:
> "scsi_target: representation of a scsi target, for now,
> this is only used for single_lun devices." This is just above
> the definition of the scsi_target structure in scsi_device.h
Yes, I suppose that's historical junk now.
> Elsewhere in that file scsi_device::single_lun is defined
> with this comment:
> "Indicates we should only allow I/O to one of the luns for
> the device at a time."
> That implies that the target must have multiple lus when
> single_lun is set :-)
>
> Is it too late to rename that field to something like:
> serialize_lu_io or single_lu_io ?
Well, it corresponds to BLIST_SINGLELUN flag, so the naming scheme is
currently internally consistent.
James
prev parent reply other threads:[~2005-02-16 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 0:57 scsi_device::single_lun name change Douglas Gilbert
2005-02-16 1:53 ` James Bottomley [this message]
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=1108518839.5539.93.camel@mulgrave \
--to=james.bottomley@steeleye.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