From: Erik Andersen <andersen@codepoet.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: [PATCH] initcall dependency solution.
Date: Fri, 7 Jun 2002 01:26:37 -0600 [thread overview]
Message-ID: <20020607072636.GA20454@codepoet.org> (raw)
In-Reply-To: <E17G94u-0000K4-00@wagner.rustcorp.com.au>
On Fri Jun 07, 2002 at 12:02:11PM +1000, Rusty Russell wrote:
> This patch allows you to name initcall dependencies and subsystems.
> It is backward compatible with the current initcall levels, but
> doesn't respect link order: a couple of changes to make it boot, but
> more will be needed I expect.
Interesting. So in theory this mechanism could also be used
to speed booting by parallelizing execution of each independent
initcall dependancy tree...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-06-07 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 2:02 [PATCH] initcall dependency solution Rusty Russell
2002-06-07 7:26 ` Erik Andersen [this message]
2002-06-07 10:15 ` Rusty Russell
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=20020607072636.GA20454@codepoet.org \
--to=andersen@codepoet.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/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