From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Olaf Hering <olaf@aepfle.de>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make prepare_namespace() wait for devices
Date: Thu, 24 May 2007 22:46:48 +0200 [thread overview]
Message-ID: <4655F9B8.8080703@drzeus.cx> (raw)
In-Reply-To: <20070524183509.GA30518@aepfle.de>
Olaf Hering wrote:
> On Thu, May 24, Pierre Ossman wrote:
>
>
>> init: wait for asynchronously scanned block devices
>>
>
> init/do_mounts.c:242:__setup("rootdelay=", root_delay_setup);
>
> Why does that not work for you and how does your patch fix it?
>
The problem isn't really mine, I just got the ball when it came to
fixing it. :)
The problem with rootdelay= is that it's a hammer when the problem
requires a screw driver. In order to get reliability, you need to whack
it hard and give it a long delay. But that has the unpleasant side
effect of having the boot taking way much more time than it really needs.
The original thread is here:
http://marc.info/?t=117879392100022&r=1&w=2
At the end of that thread I suggest a more universal approach, which I
submitted for comments here:
http://marc.info/?t=117914570700004&r=1&w=2
I believe this is a more clean approach than forcing all subsystems to
be synchronous.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-05-24 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 12:21 [PATCH] Make prepare_namespace() wait for devices Pierre Ossman
2007-05-24 18:35 ` Olaf Hering
2007-05-24 20:46 ` Pierre Ossman [this message]
2007-05-25 0:06 ` Andrew Morton
2007-05-25 4:03 ` Pierre Ossman
2007-05-25 4:17 ` Andrew Morton
2007-05-25 4:31 ` Pierre Ossman
2007-05-31 11:20 ` Pierre Ossman
2007-05-31 15:51 ` Andrew Morton
2007-06-01 5:24 ` Pierre Ossman
2007-06-01 6:40 ` Andrew Morton
2007-06-01 6:51 ` Pierre Ossman
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=4655F9B8.8080703@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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