From: James Bottomley <James.Bottomley@SteelEye.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: struct class question
Date: Wed, 29 Jun 2005 19:30:27 -0400 [thread overview]
Message-ID: <1120087827.5866.20.camel@mulgrave> (raw)
In-Reply-To: <42C328D5.7050602@adaptec.com>
On Wed, 2005-06-29 at 19:03 -0400, Luben Tuikov wrote:
> > exist at all if we can't do anything with it, I suppose that depends on
> > whether it's necessary to the tree representation or not (a bit like
> > channels in SCSI. They have meaning, but no sysfs representation on
> > their own).
>
> Very good analogy. In this respect I think we should represent
> phys, ports, and expanders just as the discover process sees them,
> in the same way, as you pointed out, channels are represented
> even though the do not quite exist (but are an abstraction).
Right, the question really is can we do anything with it, so targets
have properties (as do devices) but currently we have no channel
properties.
All SCSI devices have "ports" as defined by SAM; however, we don't show
them (well, except FC rports) because we don't use them for anything.
As far at least as SAS expanders go, I believe they do have properties
(the routing table etc.) which the driver can query, so they might be
worth adding a device for.
> Is this
>
> /sys/class/scsi_host/host1
>
> Or is it (e.g.),
>
> /sys/devices/pci0000:00/0000:00:1f.2/host1
The latter (that's the devices tree under /sys/devices).
James
prev parent reply other threads:[~2005-06-29 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:28 struct class question Luben Tuikov
2005-06-29 22:01 ` James Bottomley
2005-06-29 23:03 ` Luben Tuikov
2005-06-29 23:30 ` 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=1120087827.5866.20.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.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