All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Add support for asynchronous scans to libata
Date: Tue, 12 Dec 2006 09:02:32 -0500	[thread overview]
Message-ID: <457EB678.6010507@pobox.com> (raw)
In-Reply-To: <20061211160945.GC21070@parisc-linux.org>

Matthew Wilcox wrote:
> On Mon, Dec 11, 2006 at 10:58:06AM -0500, Jeff Garzik wrote:
>> The time-consuming portion already takes place in a thread.  Do you mean 
>> multiple threads?  Or, ATA's scan is in one thread, while work continues 
>> in other threads?
>>
>> Patch seems sane, provided that I am educated a bit :)
> 
> Each host will be scanned in its own thread.  So boot-up and
> initialisation of other devices (eg, USB, networking, PS/2, etc) will
> continue.  Drive ordering and numbering is maintained, and the default
> configuration right now is to not enable this feature.
> 
> We have infrastructure in place to make sure that all discs are found
> before we try to start init or autorun RAID.  If there's anywhere we're
> missing a call to scsi_complete_async_scans(), it'll affect SCSI as much
> as it will IDE, and I'm extremely interested in fixing it.

oh, err, hum.

libata uses one scsihost per port, not one-per-controller, so it won't 
work like you think.

This will conflict with AHCI's staggered spin-up, at least.

	Jeff




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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 21:12 [PATCH] Add support for asynchronous scans to libata Matthew Wilcox
2006-12-11 15:58 ` Jeff Garzik
2006-12-11 16:09   ` Matthew Wilcox
2006-12-12 14:02     ` Jeff Garzik [this message]
2006-12-11 16:18 ` Jeff Garzik
2006-12-12  5:02   ` Matthew Wilcox
2006-12-12  5:14     ` Matthew Wilcox
2007-04-02 13:21 ` James Smart

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=457EB678.6010507@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.