From: William Park <opengeometry@yahoo.ca>
To: "David N. Welton" <davidw@dedasys.com>
Cc: Daniel Drake <dsd@gentoo.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
viro@parcelfarce.linux.theplanet.co.uk, helge.hafting@hist.no
Subject: Re: rootdelay
Date: Mon, 25 Apr 2005 10:42:13 -0400 [thread overview]
Message-ID: <20050425144213.GA2293@node1.opengeometry.net> (raw)
In-Reply-To: <87pswjur3c.fsf@dedasys.com>
On Mon, Apr 25, 2005 at 11:45:59AM +0200, David N. Welton wrote:
> Daniel Drake <dsd@gentoo.org> writes:
>
> [ Please CC replies to me - thanks! ]
>
> > Hi David,
>
> > David N. Welton wrote:
>
> > > [ Please CC replies to me, thanks! ]
>
> > > Hi, I was looking at your patch:
>
> > > http://lkml.org/lkml/2005/1/21/132 Very small, which is nice. I
>
> > > was wondering if there were any interest in my own efforts in that
> > > direction:
>
> > > http://dedasys.com/freesoftware/patches/blkdev_wakeup.patch which
>
> > > is far more intrusive, and perhaps isn't good kernel programming
> > > style, but, on the other hand, is the optimal solution in terms of
> > > boot time because it wakes up the boot process right when the
> > > device comes on line. Since I saw your patch included, it looks
> > > like there is interest in this, and I'd toot my own horn once more
> > > before just leaving my patch to the bit rot of the ages...
> > > Thanks!
>
> > As simple as it may be, it's a bit of a shame that we actually need
> > rootdelay as its something that the kernel should do
> > automatically. At the time when we last discussed it, we didn't come
> > up with a better (and safe) way to handle it, but I don't think we
> > considered anything like your implementation.
>
> > I've CC'd a few people who were involved the last time around to see
> > if they have any input for you.
>
> Thanks! I don't wish to be a pest, but not having heard a "no", I'll
> send another ping out. Perhaps a simple description is better than
> the patch for busy people:
>
> In init/do_mounts.c, mount_root does an interruptible_sleep_on a
> wait queue, and goes on about its business after register_blkdev
> in drivers/block/genhd.c does a wake_up_interruptible on it, so
> that mounting the root device happens exactly when it needs to, no
> sooner, no later, and doesn't depend on any fiddly timing issues.
Post your patch to the list, and I'll get it from a newsgroup.
--
William Park <opengeometry@yahoo.ca>, Toronto, Canada
Slackware Linux -- because it works.
next prev parent reply other threads:[~2005-04-25 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 18:05 rootdelay David N. Welton
2005-04-01 18:27 ` rootdelay Daniel Drake
2005-04-25 9:45 ` rootdelay David N. Welton
2005-04-25 14:42 ` William Park [this message]
2005-04-25 21:34 ` rootdelay David N. Welton
2005-04-29 18:34 ` rootdelay William Park
2005-05-03 8:07 ` rootdelay David N. Welton
2005-05-03 11:13 ` rootdelay David Welton
2005-04-26 10:11 ` rootdelay Pekka Enberg
2005-04-26 19:54 ` rootdelay David N. Welton
2005-04-27 8:01 ` rootdelay Pekka Enberg
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=20050425144213.GA2293@node1.opengeometry.net \
--to=opengeometry@yahoo.ca \
--cc=akpm@osdl.org \
--cc=davidw@dedasys.com \
--cc=dsd@gentoo.org \
--cc=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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