public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, dsd@gentoo.org,
	mdharm-usb@one-eyed-alien.net, linux-usb@vger.kernel.org,
	vegardno@ifi.uio.no, James.Bottomley@HansenPartnership.com,
	linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [RFC/PATCH] usb-storage: wait for device scanning before mounting root
Date: Thu, 19 Jun 2008 12:54:19 -0600	[thread overview]
Message-ID: <20080619185419.GN4392@parisc-linux.org> (raw)
In-Reply-To: <485AA7EA.6080105@s5r6.in-berlin.de>

On Thu, Jun 19, 2008 at 08:39:38PM +0200, Stefan Richter wrote:
> The problem is AFAIU not exactly how many Scsi_Host instances (initiator 
> port representations, or something remotely related to that) are 
> instantiated, but rather _when_ they are instantiated.  On multi 
> protocol buses or networks like USB and FireWire, it makes sense to 
> create the SCSI initiator port representation when we discovered that 
> there are actually SCSI targets on the bus or network.

I'm not convinced of that.  Why shouldn't we create one scsi host for
all USB scsi devices?  I know that today there's a certain amount of
per-device state stored in the scsi_host, but that should be fixable.

> scsi_scan's API is geared towards drivers which create one or more 
> initiator port representations right up front before going on target 
> discovery, right?

Today, yes.  The mail that I just pinged described a way to enhance the
API -- letting you tell scsi "I've started scanning, save me a place in
the queue" and "I've finished scanning, hook me up".

The advantage to this is that you can spend a lot more time waiting for
devices without increasing boot time significantly, since you wait while
the rest of the system initialises.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  parent reply	other threads:[~2008-06-19 18:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 20:21 [RFC/PATCH] usb-storage: wait for device scanning before mounting root Pekka J Enberg
2008-04-24 21:08 ` Alan Stern
2008-04-24 21:25   ` Pekka J Enberg
2008-04-24 22:56     ` Greg KH
2008-04-24 23:30       ` Matthew Dharm
2008-04-25  6:30         ` Pekka J Enberg
2008-04-25  7:04           ` Matthew Dharm
2008-04-25  8:19             ` Pekka J Enberg
2008-04-25 15:35               ` Matthew Dharm
2008-04-25 16:05               ` Greg KH
2008-04-25  6:09       ` Pekka J Enberg
2008-04-25  7:53     ` Stefan Richter
2008-04-25  8:15       ` Pekka J Enberg
2008-04-25  9:11         ` Matthew Wilcox
2008-06-19 18:23           ` Matthew Wilcox
2008-06-19 18:39             ` Stefan Richter
2008-06-19 18:43               ` Stefan Richter
2008-06-19 18:54               ` Matthew Wilcox [this message]
2008-06-19 19:52                 ` Matthew Dharm
2008-06-19 20:49                   ` Matthew Wilcox
2008-06-19 21:19                     ` Stefan Richter
2008-06-19 19:54                 ` Stefan Richter
2008-06-19 20:22                   ` Matthew Wilcox
2008-06-19 20:34                     ` Stefan Richter
2008-06-19 21:39             ` Alan Stern
2008-06-19 23:13               ` David Brownell
2008-06-20  9:53                 ` Gabor Gombas
2008-06-20 14:14                   ` Matthew Dharm
2008-06-20 15:15               ` Vegard Nossum
2008-06-20 15:31                 ` Matthew Wilcox
2008-06-20 15:42                 ` Alan Stern
2008-06-20 16:37                   ` Stefan Richter

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=20080619185419.GN4392@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dsd@gentoo.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=penberg@cs.helsinki.fi \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stern@rowland.harvard.edu \
    --cc=vegardno@ifi.uio.no \
    /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