From: Christoph Hellwig <hch@lst.de>
To: Mike Christie <michaelc@cs.wisc.edu>,
iscsi -devel <linux-iscsi-devel@lists.sourceforge.net>,
David Wysochanski <davidw@netapp.com>,
"Surekha.PC" <surekhap@cisco.com>,
linux-scsi@vger.kernel.org
Subject: Re: [linux-iscsi-devel] Re: [PATCH RFC] replace ioctl for sysfs take 2
Date: Mon, 6 Sep 2004 16:32:51 +0200 [thread overview]
Message-ID: <20040906143251.GB21646@lst.de> (raw)
In-Reply-To: <20040901162042.GC26753@null.msp.redhat.com>
On Wed, Sep 01, 2004 at 11:20:42AM -0500, AJ Lewis wrote:
> Do we want all these attributes in the scsi_host class, or should we put them
> in the iscsi devices directory? So in /sys/bus/iscsi-sfnet/devices/iscsi1 -
> it seems to me these attributes are specific to the iscsi target, and don't
> need to be in the scsi_host class.
I think all attributes that are common over software- and hardware based
iscsi implementations should go into a iscsi transport class. Of course
it's hard to without a hardware driver to work with. I remember Qlogic
said they wanted to submit their driver some time in the future, maybe
one of their developers is listening on linux-scsi.
next parent reply other threads:[~2004-09-06 14:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <413557CB.8010008@cs.wisc.edu>
[not found] ` <20040901162042.GC26753@null.msp.redhat.com>
2004-09-06 14:32 ` Christoph Hellwig [this message]
2004-09-06 16:33 ` [linux-iscsi-devel] Re: [PATCH RFC] replace ioctl for sysfs take 2 Matthew Wilcox
2004-09-06 18:15 ` Mike Christie
2004-09-06 18:54 ` Mike Christie
2004-09-06 22:48 ` Mike Christie
2004-09-06 23:11 ` James Bottomley
2004-09-07 2:46 ` Mike Christie
2004-09-07 15:35 ` James Bottomley
2004-09-07 19:19 ` Scott M. Ferris
2004-09-07 20:42 ` James Bottomley
2004-09-07 21:05 ` Scott M. Ferris
2004-09-07 21:12 ` Mike Christie
2004-09-07 21:24 ` Scott M. Ferris
2004-09-07 21:33 ` James Bottomley
2004-09-07 21:37 ` Mike Christie
2004-09-07 22:05 ` James Bottomley
2004-09-07 22:40 ` Mike Christie
2004-09-07 22:57 ` Mike Christie
2004-09-08 10:27 ` Mike Christie
2004-09-07 23:34 ` James Bottomley
2004-09-08 9:19 ` Mike Christie
2004-09-08 14:53 ` James Bottomley
2004-09-07 21:14 ` James Bottomley
2004-09-08 2:33 ` Douglas Gilbert
2004-09-08 14:38 ` Randy.Dunlap
2004-09-08 18:11 ` Bryan Henderson
2004-09-09 0:40 ` Douglas Gilbert
2004-09-09 15:40 ` AJ Lewis
2004-09-07 15:24 ` AJ Lewis
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=20040906143251.GB21646@lst.de \
--to=hch@lst.de \
--cc=davidw@netapp.com \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=surekhap@cisco.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