mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] async scsi scanning, version 13
Date: Mon, 02 Oct 2006 12:02:14 +0200	[thread overview]
Message-ID: <4520E3A6.7030907@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061001201753.GG16272@parisc-linux.org>

Matthew Wilcox wrote:
> Add ability to scan scsi busses asynchronously
> 
> Since it often takes around 20-30 seconds to scan a scsi bus, it's
> highly advantageous to do this in parallel with other things.  The bulk
> of this patch is ensuring that devices don't change numbering, and that
> all devices are discovered prior to trying to start init.  For those
> who build SCSI as modules, there's a new scsi_wait_scan module that will
> ensure all bus scans are finished.
> 
> This patch only handles drivers which call scsi_scan_host.  Fibre Channel,
> SAS, SATA, USB and Firewire all need additional work.

A note on FireWire/ SBP-2's status: We basically scan* asynchronously,
although the scans are serialized across all FireWire devices on all
buses. Parallelized scanning is on my long term to-do list. Serialized
scanning is actually quick enough unless something goes wrong.

Integration of sbp2 with scsi_wait_scan is now on my to-do list too. It
is orthogonal to parallelized scanning as a feature but probably
somewhat coupled when it comes to an actual implementation.

So far, the few people who have the root filesystem (or any other
filesystem that they want to have ready on boot) on an SBP-2 disk simply
put a sleep into their initrd or run a more or less complete hotplug
environment from initrd. The scsi_wait_scan module would certainly be
more comfortable than that.

[ *) "scan" = read ISO 13213 configuration ROMs, then run protocol
     driver probes including sbp2's login ]
-- 
Stefan Richter
-=====-=-==- =-=- ---=-
http://arcgraph.de/sr/

      reply	other threads:[~2006-10-02 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 21:19 Matthew Wilcox
2006-10-01 20:00 ` James Bottomley
2006-10-01 20:17   ` Matthew Wilcox
2006-10-02 10:02     ` Stefan Richter [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=4520E3A6.7030907@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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

all inboxes | Powered by JetHome®