From: Luben Tuikov <luben_tuikov@adaptec.com>
To: dougg@torque.net
Cc: Christoph Hellwig <hch@infradead.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
andrew.patterson@hp.com, Eric.Moore@lsil.com, mike.miller@hp.com,
Madhuresh_Nagshain@adaptec.com
Subject: Re: [RFC] SAS domain layout for Linux sysfs
Date: Wed, 27 Apr 2005 11:38:33 -0400 [thread overview]
Message-ID: <426FB1F9.9010401@adaptec.com> (raw)
In-Reply-To: <426F86D3.4070909@torque.net>
On 04/27/05 08:34, Douglas Gilbert wrote:
> Once the SAS discovery algorithm has been run should we
> show its results in sysfs?? We probably want to know
> about SCSI target devices (like we do for other transports).
> The SAS discovery algorithm may have found other interesting
> things:
> - other expanders (beyond what the silicon has seen)
> - other initiators (implies a multi initiator environment)
> - miswired SAS domains (since SAS expander routing rules
> have restrictions)
Yes, I think we should know about those other devices, part
of SAS SDS.
> Other tools may want to access SMP (and SCSI log pages
> in SCSI target devices) to identify bottlenecks and access
> vendor extensions.
Yes, very true. I can imagine user space apps sending SMP
and what not to expanders/RAID devices/enclosures past
expanders, to control the storage network.
A sysfs representation of the discovery result could make this
easy, since as you pointed out expanders are not SAS devices,
and thus do not fit the linux-scsi HCTL space.
Luben
next prev parent reply other threads:[~2005-04-27 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 15:22 [RFC] SAS domain layout for Linux sysfs Luben Tuikov
2005-04-24 11:19 ` Christoph Hellwig
2005-04-25 16:06 ` Luben Tuikov
2005-04-25 16:14 ` Christoph Hellwig
2005-04-25 17:21 ` Luben Tuikov
2005-04-25 18:18 ` Christoph Hellwig
2005-04-26 15:18 ` Luben Tuikov
2005-04-27 12:34 ` Douglas Gilbert
2005-04-27 15:38 ` Luben Tuikov [this message]
2005-04-29 10:08 ` Christoph Hellwig
2005-05-02 14:35 ` Luben Tuikov
2005-04-29 10:05 ` Christoph Hellwig
2005-05-02 14:30 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 14:54 Martin Peschke3
2005-04-27 15:52 ` Luben Tuikov
2005-04-27 18:57 ` David S. Miller
2005-06-01 21:49 Moore, Eric Dean
2005-06-02 14:32 Miller, Mike (OS Dev)
2005-06-02 14:57 ` 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=426FB1F9.9010401@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=Eric.Moore@lsil.com \
--cc=Madhuresh_Nagshain@adaptec.com \
--cc=andrew.patterson@hp.com \
--cc=dougg@torque.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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