From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
npiggin@suse.de, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains
Date: Mon, 30 Jul 2007 10:53:27 -0700 [thread overview]
Message-ID: <20070730175326.GC10033@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070729211644.GC6808@elte.hu>
On Sun, Jul 29, 2007 at 11:16:44PM +0200, Ingo Molnar wrote:
>
> * Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:
>
> > They might be doing more exec's and probably covered by exec balance.
> >
> > There was a small pthread test case which was calculating the time to
> > create all the threads and how much time each thread took to start
> > running. It appeared as if the threads ran sequentially one after
> > another on a DP system with four cores leading to this SD_BALANCE_FORK
> > observation.
>
> would be nice to dig out that testcase i suspect and quantify the
> benefits of your patch.
That test case doesn't do much other than calculating the time taken for each
thread to start running. With this balance on fork patch, that small pthread
test case shows that all the threads now start almost at the same time on all
cores.
> Another workload which might perform better
> would be linpack: it benefits from fast and immediate 'spreading' of
> freshly forked threads.
My understanding is that linkpack doesn't do fork often(as such
difference might not be visible, but will take a look). We were planning
to test httperf or some other workloads which probably does fork more often.
thanks,
suresh
prev parent reply other threads:[~2007-07-30 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:32 [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains Siddha, Suresh B
2007-07-26 22:18 ` Ingo Molnar
2007-07-26 22:34 ` Siddha, Suresh B
2007-07-27 1:22 ` Nick Piggin
2007-07-27 19:09 ` Siddha, Suresh B
2007-07-29 21:16 ` Ingo Molnar
2007-07-30 17:53 ` Siddha, Suresh B [this message]
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=20070730175326.GC10033@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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