From: Christoph Hellwig <hch@infradead.org>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: dougg@torque.net, andrew.patterson@hp.com, Eric.Moore@lsil.com,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Luben Tuikov <luben_tuikov@adaptec.com>,
Madhuresh_Nagshain@adaptec.com, mike.miller@hp.com
Subject: Re: [RFC] SAS domain layout for Linux sysfs
Date: Fri, 29 Apr 2005 11:11:01 +0100 [thread overview]
Message-ID: <20050429101101.GC3342@infradead.org> (raw)
In-Reply-To: <OF4CE413A0.DAB8B74B-ONC1256FF0.00505593-C1256FF0.0052A229@de.ibm.com>
On Wed, Apr 27, 2005 at 04:54:53PM +0200, Martin Peschke3 wrote:
> Similarly, in the case of Fibre Channel, a common N_Port or
> SCSI target device discovery, preferably in user space, seems
> to be desirable.
Did I tell you zfcp needs some updates to use all features of the FC
transport class?
> This would require some CT and / or ELS
> passthrough interface, for example in order to issue queries
> to fabric switches.
Emulex plans to contribute such interfaces to the FC transport class.
It would be nice if zfcp could catch up on full usage of the transport
class, or did I mention that already? ;-)
next prev parent reply other threads:[~2005-04-29 10:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 14:54 [RFC] SAS domain layout for Linux sysfs Martin Peschke3
2005-04-27 15:52 ` Luben Tuikov
2005-04-27 18:57 ` David S. Miller
2005-04-29 10:11 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 14:32 Miller, Mike (OS Dev)
2005-06-02 14:57 ` Luben Tuikov
2005-06-01 21:49 Moore, Eric Dean
2005-04-13 15:22 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
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
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=20050429101101.GC3342@infradead.org \
--to=hch@infradead.org \
--cc=Eric.Moore@lsil.com \
--cc=MPESCHKE@de.ibm.com \
--cc=Madhuresh_Nagshain@adaptec.com \
--cc=andrew.patterson@hp.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--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