From: Mike Christie <michaelc@cs.wisc.edu>
To: Matthew Wilcox <willy@debian.org>
Cc: Christoph Hellwig <hch@lst.de>,
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, 06 Sep 2004 11:15:00 -0700 [thread overview]
Message-ID: <413CA924.8030904@cs.wisc.edu> (raw)
In-Reply-To: <20040906163336.GE642@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Mon, Sep 06, 2004 at 04:32:51PM +0200, Christoph Hellwig wrote:
>
>>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 -
>
>
> Woah, woah, woah. What's this "iscsi-sfnet" directory in sysfs? That's
> just wrong.
It is only a pseudo bus for the driver from Christoph's suggestion,
that's just to make probing and removing of the driver's devices easier (it
looks like a normal scsi driver now).
No way is that crap going into the kernel. We have to have
> *one* iscsi infrastructure, not a dozen.
>
Don't worry, there is no way we are going to put transport, scsi or
anything like that there. This driver will use the scsi-ml infrastucture
for sysfs and this includes using the transport classes. I think this comment
from AJ, was just in error when he was unaware of scsi-ml's transport classes.
next prev parent reply other threads:[~2004-09-06 18:15 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 ` [linux-iscsi-devel] Re: [PATCH RFC] replace ioctl for sysfs take 2 Christoph Hellwig
2004-09-06 16:33 ` Matthew Wilcox
2004-09-06 18:15 ` Mike Christie [this message]
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=413CA924.8030904@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=davidw@netapp.com \
--cc=hch@lst.de \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=surekhap@cisco.com \
--cc=willy@debian.org \
/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