[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5403ADA8.1090903@linux.intel.com>
Date: Sun, 31 Aug 2014 16:20:08 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Tejun Heo <tj@...nel.org>, Greg KH <gregkh@...uxfoundation.org>
CC: Dmitry Torokhov <dmitry.torokhov@...il.com>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>, falcon@...zu.com,
tiwai@...e.de, linux-kernel@...r.kernel.org, oleg@...hat.com,
akpm@...ux-foundation.org, penguin-kernel@...ove.sakura.ne.jp,
joseph.salisbury@...onical.com, bpoirier@...e.de,
"Luis R. Rodriguez" <mcgrof@...e.com>
Subject: Re: [RFC v1 0/3] driver-core: add asynch module loading support
On 8/31/2014 3:53 PM, Tejun Heo wrote:
> Hello,
>
> On Sun, Aug 31, 2014 at 03:15:34PM -0700, Greg KH wrote:
>> For the use cases we have today, it would work. We have a few drivers
>> that take a _long_ time in their probe callback, and they need to be
>> made async for various reasons (modprobe timeout killer, touchscreen
>> init sequence stalling boot, etc.)
>
> Oh, but there already is a reported case which fails. Hard drives
> with a lot of platters take > 10secs to spin up and there are
> configurations which regularly fail the initial reset and it's quite
> rare but probing time taking over 30s does happen in the wild. We
> can't mark libata as requiring async probing on module load
> unconditionally but at the same time we need them to be asynchronous
> for use cases which don't depend on synchronous behavior has has
> timeout.
libata probing is already async thankfully.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists