From: Mike Anderson <andmike@us.ibm.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Christoph Hellwig <hch@lst.de>,
James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] pull scsi_scan_host out of scsi_add_host
Date: Tue, 8 Jul 2003 08:56:45 -0700 [thread overview]
Message-ID: <20030708155645.GA4379@beaverton.ibm.com> (raw)
In-Reply-To: <200307081103.17131.oliver@neukum.org>
Oliver Neukum [oliver@neukum.org] wrote:
> Am Dienstag, 8. Juli 2003 10:03 schrieb Mike Anderson:
> > Christoph Hellwig [hch@lst.de] wrote:
> > > As Douglas mentioned on this list a while ago there's hardware these
> > > days where we don't want to automatically perform an initial bus scan
> > > in scsi_add_host. Currently we only have ieee1394 in the tree but
> > > I can imagine more uses like iscsi or certain fc setups.
> > >
> > > This patch removes the call to scsi_scan_host from scsi_add_host
> > > and moves it into the drivers that want in.
> >
> > Would we want to make a symmetric interface and pull the
> > unscan out of scsi_remove_host also?
>
> Unless you are talking about multipath, you have to forget
> all devices connected to a controller, so what sense would
> it make?
Probably not much sense. I was thinking of a progression to user assisted
scanning. In that a driver could never call scsi_scan_host directly and
conversely never call scsi_forget_host directly.
But in the removal case there is not much response a user space hotplug
handler could make besides a delayed call to scsi_remove_device.
>
> Philosophically speaking, scanning is an operation that cannot
> be simply undone. You can undo device/driver bindings but you
> cannot undo a bus scan.
Maybe it was a confusing choice of words. The operation I was describing
was to undo the binding.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-07-08 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 14:30 [PATCH] pull scsi_scan_host out of scsi_add_host Christoph Hellwig
2003-07-08 8:03 ` Mike Anderson
2003-07-08 8:23 ` Christoph Hellwig
2003-07-08 9:03 ` Oliver Neukum
2003-07-08 15:56 ` 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=20030708155645.GA4379@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.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