public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Martin Hicks <mort@wildopensource.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Transport Attributes -- attempt#2
Date: 08 Jan 2004 09:11:26 -0500	[thread overview]
Message-ID: <1073571086.2741.5.camel@mulgrave> (raw)
In-Reply-To: <20040108140155.GD30627@localhost>

On Thu, 2004-01-08 at 09:01, Martin Hicks wrote:
> > >> Out of curiosity:  Why do we need _another_ classdev.  Can't you
> > >> reuse the current one?
> 
> It guess we could re-use the scsi_device classdev.  This would mean that
> all the attribute files would show up in /sys/class/scsi_device/w:x:y:z.
> We would have to export an attribute called "transport" to tell which
> transport the device is using.  I'm agreeable to this solution.  I don't
> much like having an fc_transport and pscsi_transport directory in
> /sys/class.

I disagree with this.  We put attributes that apply to all devices in
scsi_device classdev.  We're implementing a separate transport interface
here, so it really does need its own class_device, otherwise separating
it from scsi_sysfs and allowing arbitrary transport class creation will
become a real pain.

A class is supposed to represent a device interface, and the transport
class does just that for transport attributes.

James



  reply	other threads:[~2004-01-08 14:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 18:54 Transport Attributes -- attempt#2 Martin Hicks
2004-01-08 13:17 ` Christoph Hellwig
2004-01-08 14:01   ` Martin Hicks
2004-01-08 14:11     ` James Bottomley [this message]
2004-01-14 18:12   ` Transport Attributes -- attempt#3 Martin Hicks
2004-01-14 23:34     ` Andrew Vasquez
2004-01-16 16:40       ` Martin Hicks
2004-01-17  0:23       ` Lincoln Dale
2004-01-14 23:58     ` Patrick Mansfield
2004-01-16 14:54     ` Christoph Hellwig
2004-01-16 16:54       ` Martin Hicks
2004-01-20  0:07     ` Brian King
2004-01-20 19:49       ` Patrick Mansfield
2004-01-20 20:38         ` Brian King
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 23:24 Transport Attributes -- attempt#2 christophe.varoqui

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=1073571086.2741.5.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mort@wildopensource.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