From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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,
dougg@torque.net, Madhuresh_Nagshain@adaptec.com
Subject: Re: [RFC] SAS domain layout for Linux sysfs
Date: Tue, 26 Apr 2005 11:18:07 -0400 [thread overview]
Message-ID: <426E5BAF.4040003@adaptec.com> (raw)
In-Reply-To: <20050425181831.GA14190@infradead.org>
On 04/25/05 14:18, Christoph Hellwig wrote:
> The point is that discovery must happen for each HBA separately because
> we absolutely do not want to have global state.
OK.
Can you please define "global state"?
In SAS, when the domain changes, the controller(s) connected to the
domain get notification and pass it to the discovery process, which
will run again.
Overall, since the discovery process gets (internally) a "picture"
of the domain out there, it would be appropriate to show this
"picture" to the user.
Luben
next prev parent reply other threads:[~2005-04-26 15:22 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 [this message]
2005-04-27 12:34 ` Douglas Gilbert
2005-04-27 15:38 ` Luben Tuikov
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=426E5BAF.4040003@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