[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 May 2009 17:55:39 -0700
From: David VomLehn <dvomlehn@...co.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
linux-usb@...r.kernel.org, greg@...ah.com,
linux-scsi@...r.kernel.org, netdev@...r.kernel.org,
arjan@...radead.org
Subject: Re: [PATCH 1/5] initdev:kernel: Asynchronously-discovered device
synchronization, v5
On Sat, May 02, 2009 at 01:55:45PM -0400, Alan Stern wrote:
> On Sat, 2 May 2009, James Bottomley wrote:
...
> > What I'm getting at is that I don't see the benefit of this in the light
> > of Arjan's async boot system, which can also tell us when all discovery
> > is complete ... what added benefit am I missing here?
>
> How does Arjan's async boot system tell use when all discovery is
> complete? AFAICS, it only tells you when all its async tasks are
> finished. But device discovery and registration sometimes use other
> asynchronous techniques which Arjan's code is unaware of. Examples:
> the USB khubd thread, the USB mass-storage scanning thread, and the
> SCSI async-scanning thread.
The patchset does use Arjan's asynchronous function calls in one place. If
there are other places it can be used to get equivalent functionality, I'll
be happy to do so.
> Alan Stern
David VomLehn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists