From: Arjan van de Ven <arjan@infradead.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 1/3] fastboot: Create a "asynchronous" initlevel
Date: Fri, 18 Jul 2008 21:58:47 -0700 [thread overview]
Message-ID: <20080718215847.3db0dc9e@infradead.org> (raw)
In-Reply-To: <1216440697.3978.142.camel@localhost.localdomain>
On Fri, 18 Jul 2008 21:11:37 -0700
Daniel Walker <dwalker@mvista.com> wrote:
> On Fri, 2008-07-18 at 20:44 -0700, Arjan van de Ven wrote:
> > On Fri, 18 Jul 2008 18:22:20 -0700
> > Daniel Walker <dwalker@mvista.com> wrote:
> >
> > > On Fri, 2008-07-18 at 15:16 -0700, Arjan van de Ven wrote:
> > > > +static void __init do_initcalls(void)
> > > > +{
> > > > + initcall_t *call;
> > > > + static DECLARE_WORK(async_work, do_async_initcalls);
> > > > + int phase = 0; /* 0 = levels 0 - 6, 1 = level 6a, 2 =
> > > > after level 6a */
> > > > +
> > > > + async_init_wq =
> > > > create_singlethread_workqueue("kasyncinit"); +
> > >
> > > Could you spawning one thread per cpu, and queuing the work
> > > evenly?
> >
> > not without loosing the ordering.....
> >
>
> I don't think there is any expectation for any given initcall to have
> a special ordering .. There is an ordering expectation for say
> initcall 6 runs before 6a , but not within the initcall ..
>
that's not right.. device numbering very highly depends on that.
the specified ordering is makefile link order.
next prev parent reply other threads:[~2008-07-19 4:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 22:15 [patch 0/3] fastboot patches series 1 Arjan van de Ven
2008-07-18 22:16 ` [patch 1/3] fastboot: Create a "asynchronous" initlevel Arjan van de Ven
2008-07-19 1:22 ` Daniel Walker
2008-07-19 3:44 ` Arjan van de Ven
2008-07-19 4:11 ` Daniel Walker
2008-07-19 4:58 ` Arjan van de Ven [this message]
2008-07-19 5:20 ` Arjan van de Ven
2008-07-19 15:24 ` Daniel Walker
2008-07-19 15:35 ` Arjan van de Ven
2008-07-19 16:08 ` Daniel Walker
2008-07-19 16:14 ` Arjan van de Ven
2008-07-19 4:28 ` Daniel Walker
2008-07-19 7:53 ` Rene Herman
2008-07-19 8:10 ` Rene Herman
2008-07-19 15:44 ` Arjan van de Ven
2008-07-20 7:23 ` Rene Herman
2008-07-20 11:10 ` Arjan van de Ven
2008-07-20 14:20 ` Rene Herman
2008-07-20 15:35 ` Arjan van de Ven
2008-07-18 22:16 ` [patch 2/3] fastboot: turn the USB hostcontroller initcalls into async initcalls Arjan van de Ven
2008-07-18 22:17 ` [patch 3/3] fastboot: convert a few non-critical ACPI drivers to " Arjan van de Ven
2008-07-19 4:51 ` [patch 0/3] fastboot patches series 1 Simon Arlott
2008-07-19 5:16 ` Arjan van de Ven
2008-07-19 5:47 ` Simon Arlott
2008-07-19 10:22 ` Andi Kleen
2008-07-20 8:31 ` Ingo Molnar
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=20080718215847.3db0dc9e@infradead.org \
--to=arjan@infradead.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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