From: Mike Anderson <andmike@us.ibm.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Christoph Hellwig <hch@lst.de>,
James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] allow NULL dev argument to scsi_add_host
Date: Sun, 12 Jan 2003 22:50:31 -0800 [thread overview]
Message-ID: <20030113065031.GA4599@beaverton.ibm.com> (raw)
In-Reply-To: <20030112231151.GA20678@win.tue.nl>
Andries Brouwer [aebr@win.tue.nl] wrote:
> On Sun, Jan 12, 2003 at 11:40:30AM -0800, Mike Anderson wrote:
>
> > Currently we have a couple of issues that might be solved by the creation of a
> > scsi subsystem in /sysfs/scsi:
>
> Is /sysfs/scsi better than /sysfs/devices/scsiX?
The choice was not better it was just a difference of semantics. The
/sysfs/devices tree normal contains devices with an associated bus
(though you can set this to NULL). The device tree was meant to contain
real devices. The support I added to scsi_debug was to emulate a real
device so the overhead was needed to try to match the call paths of
other LLDD like some of the converted pci's. The addition of ide-scsi to
the device tree was that there was no other option.
I hoped to get a smaller object to represent the emulated scsi hosts or
hosts that had not been converted in a /sysfs/scsi subsystem. I also
thought we might need other sysfs entries related to the SCSI subsystem
(scsi logging control, sg mapping solution, scsiX host mapping "The
scsi-host class I created sucks right now").
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-01-13 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 19:33 [PATCH] allow NULL dev argument to scsi_add_host Christoph Hellwig
2003-01-11 22:32 ` Willem Riede
2003-01-12 1:17 ` Mike Anderson
2003-01-12 8:06 ` Christoph Hellwig
2003-01-12 19:40 ` Mike Anderson
2003-01-12 23:11 ` Andries Brouwer
2003-01-13 6:50 ` Mike Anderson [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=20030113065031.GA4599@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=aebr@win.tue.nl \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.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