From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] add sysfs attributes to scan and delete scsi_devices
Date: Tue, 8 Jul 2003 15:24:40 -0700 [thread overview]
Message-ID: <20030708152440.A373@beaverton.ibm.com> (raw)
In-Reply-To: <20030708221350.A19804@infradead.org>; from hch@infradead.org on Tue, Jul 08, 2003 at 10:13:51PM +0100
On Tue, Jul 08, 2003 at 10:13:51PM +0100, Christoph Hellwig wrote:
> On Tue, Jul 08, 2003 at 03:50:15PM -0500, James Bottomley wrote:
> > I'm not convinced we need a bus file for this. What's the reason we
> > can't have a per host file instead?
> >
> > I'm thinking of the hotplug case where you know the sysfs path to the
> > card just inserted. Translating that to a hostid will be rather hard.
>
> After thinking about this again I tend to agree with you that a per-host
> file sounds like the better idea.
James/Christoph -
There is not much of a difference either way.
Scanning makes more sense as a host attribute (or as a target attribute,
but we don't have a target device today). Deletion of a scsi_device makes
more sense as a /sysfs/bus/scsi (or even scsi_device) attribute that takes
a bus_id.
But we should be symmetrical for a user space interface. (And it is easier
to catch sscanf errors using spaces as a separator.)
I'll go ahead and redo it as per-host, and move string parsing into
scsi_sysfs.c.
Thanks for the feedback.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-07-08 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:40 [PATCH] add sysfs attributes to scan and delete scsi_devices Patrick Mansfield
2003-07-08 20:41 ` examples using " Patrick Mansfield
2003-07-08 20:47 ` [PATCH] add " Christoph Hellwig
2003-07-08 22:36 ` Patrick Mansfield
2003-07-08 20:50 ` James Bottomley
2003-07-08 21:13 ` Christoph Hellwig
2003-07-08 22:24 ` Patrick Mansfield [this message]
2003-07-13 13:43 ` Christoph Hellwig
2003-07-09 20:27 ` [PATCH] take 2 " Patrick Mansfield
2003-07-09 20:29 ` and some example usage of the attributes Patrick Mansfield
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=20030708152440.A373@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--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