linux-kernel - Re: [patch 1/3] fastboot: Create a "asynchronous" initlevel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080718222014.34754e7b@infradead.org>
Date:	Fri, 18 Jul 2008 22:20:14 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [patch 1/3] fastboot: Create a "asynchronous" initlevel

On Fri, 18 Jul 2008 21:11:37 -0700
Daniel Walker <dwalker@...sta.com> wrote: 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 ..
> 

btw it's also about learning to crawl before learning to walk, before
learning to run. THis stuff is tricky and there are many hidden
problems; I rather start SIMPLE and understandably right, I don't want
to go "full parallel" now (or maybe ever, no idea, we need to learn
from this step first). Btw: I suspect the biggest gain comes from the
first step or two.. after that you soon get diminishing returns...


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/