public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Ingo Molnar <mingo@elte.hu>, Tony Luck <tony.luck@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [GIT PULL] sched/core for v2.6.32
Date: Sun, 13 Sep 2009 08:41:54 +0200	[thread overview]
Message-ID: <1252824114.16650.130.camel@marge.simson.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0909122354260.23341@swampdragon.chaosbits.net>

On Sun, 2009-09-13 at 00:07 +0200, Jesper Juhl wrote:
> On Sat, 12 Sep 2009, Ingo Molnar wrote:
> 

> > It was a statistical property based on performance considerations - 
> > and now we flipped it around based on latency and for kbuild 
> > performance/throughput reasons: Serge Belyshev reported a 7% 
> > increase on a quad due to this change and i measured a 1.5% 
> > peak-kbuild performance increase.
> > 
> Impressive. I wouldn't have expected that much gain by running the parent 
> first. Actually I personally would have expected child-first to perform 
> better since (in my experience) it's usually the child that's just forked 
> that matters the most.

How can waiting for child1 to run a bit before forking off child2 _not_
hurt?  The parent is the worker bee creator, the queen bee if you will.
Seems to me that making the queen wait until one egg hatches and ages a
bit before laying another egg is a very bad plan if the goal is to have
a hive full of short lived worker bees.

	-Mike


  reply	other threads:[~2009-09-13  6:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 19:25 [GIT PULL] sched/core for v2.6.32 Ingo Molnar
2009-09-11 22:40 ` Jesper Juhl
2009-09-11 22:58   ` Linus Torvalds
2009-09-11 23:34     ` Jesper Juhl
2009-09-12  2:24       ` Tony Luck
2009-09-12  5:49         ` Ingo Molnar
2009-09-12 22:07           ` Jesper Juhl
2009-09-13  6:41             ` Mike Galbraith [this message]
2009-09-13 22:03               ` Jesper Juhl

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=1252824114.16650.130.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    /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