public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <alewis@redhat.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Matthew Wilcox <willy@debian.org>, 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: Tue, 7 Sep 2004 10:24:52 -0500	[thread overview]
Message-ID: <20040907152452.GB22719@null.msp.redhat.com> (raw)
In-Reply-To: <413CA924.8030904@cs.wisc.edu>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

On Mon, Sep 06, 2004 at 11:15:00AM -0700, Mike Christie wrote:
> 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. 

Yeah - that was me being ignorant of the transport classes.  Speaking of
which, is anyone working on a transport class for iscsi?  I see a patch for
one in the archives
( http://marc.theaimsgroup.com/?l=linux-scsi&m=108033504301079&w=2 ), but it
looks like the discussion sort of died off and nothing ever got accepted.  I'd
be willing to put together a patch for an iscsi transport class if no one else
is working on one right now.

Regards,
-- 
AJ Lewis                                   Voice:  612-638-0500
Red Hat Inc.                               E-Mail: alewis@redhat.com
720 Washington Ave. SE, Suite 200
Minneapolis, MN 55414
   
Current GPG fingerprint = D9F8 EDCE 4242 855F A03D  9B63 F50C 54A8 578C 8715
Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
many keyservers out there...


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-09-07 15:25 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
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 [this message]

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=20040907152452.GB22719@null.msp.redhat.com \
    --to=alewis@redhat.com \
    --cc=davidw@netapp.com \
    --cc=hch@lst.de \
    --cc=linux-iscsi-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --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