public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 19 Jul 2008 08:35:32 -0700	[thread overview]
Message-ID: <20080719083532.21c9a43e@infradead.org> (raw)
In-Reply-To: <1216481066.3978.159.camel@localhost.localdomain>

On Sat, 19 Jul 2008 08:24:26 -0700
Daniel Walker <dwalker@mvista.com> wrote:

> On Fri, 2008-07-18 at 22:20 -0700, Arjan van de Ven wrote:
> 
> > 
> > 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...
> > 
> 
> Ok .. I'm not trying to rush you .. With that said, the increased
> number of threads seems like a natural direction to take.. I would
> assume the returns would diminish depending on the number of threads
> per the hardware.. For instance , your addition of one thread might
> even harm the boot time on some single core embedded systems ..

well it still improves the cases where msleep() happens... even on
single core. (fwiw the test  machine I reported numbers from is single
core, albeit with hyperthreading)



-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-19 15:35 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
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 [this message]
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=20080719083532.21c9a43e@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