[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <484554EE.6020007@s5r6.in-berlin.de>
Date: Tue, 03 Jun 2008 16:27:58 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Andi Kleen <andi@...stfloor.org>
CC: Rick van Rein <rick@...engemak.nl>, daniel.blueman@...il.com,
david@...g.hm, linux-kernel@...r.kernel.org
Subject: Re: Future Linux on Bistable Storage
Andi Kleen wrote:
> Rick van Rein wrote:
>>> Rick van Rein <rick@...engemak.nl> writes:
>>>> Regarding I/O init: Current Linux boots while initiating one device at a
>>>> time. Some degree of serialism must exist, but after scanning a bus would
>>>> it not be possible to fork threads to initiate each of the devices found
>>>> on it?
>>>
>>> Multithreaded driver initialization has been tried, but reverted
>>> because it triggered too many driver bugs.
>>>
>> Thanks for your responses. You convinced me I/O initiatilisation cannot
>> be improved upon.
>
> I'm sure it can. It's just significant work to do it and would need
> to be done step by step. It's a bit like the "remove BKL everywhere"
> project.
Several bus subsystems actually probe asynchronously (i.e. in parallel
to other bus subsystems) or even with some degree of internal parallelism.
Of course there are notable benefits in this only if the devices are
very slow to start up --- e.g. because they contain moving parts (this
kind of devices is not present in Rick's setup) or because they are
connected via high latency interconnects --- or if there is a massive
number of devices.
--
Stefan Richter
-=====-==--- -==- ---==
http://arcgraph.de/sr/
--
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