From: Ingo Molnar <mingo@elte.hu>
To: Colin Fowler <elethiomel@gmail.com>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon
Date: Wed, 16 Jan 2008 17:19:51 +0100 [thread overview]
Message-ID: <20080116161951.GA15000@elte.hu> (raw)
In-Reply-To: <cf3edd8d0801160810w4302afa5vd731cc6852c778ba@mail.gmail.com>
* Colin Fowler <elethiomel@gmail.com> wrote:
> Hi Ingo, I'll need to convince my supervisor first if I can release a
> binary. Technically anythin glike this needs to go through our
> University's "innovations department" and requires lengthy paperwork
> and NDAs :(.
a binary wouldnt work for me anyway. But you could try to write a
"workload simulator": just pick out the pthread ops and replace the
worker functions with some dummy stuff that just touches an array that
has similar size to the tiles (in a tight loop). Make sure it has
similar context-switch rate and idle percentage as your real workload -
then send us the .c file. As long as it's a single .c file that runs for
a few seconds and outputs a precise enough "run time" result, kernel
developers would pick it up and use it for optimizations. To get the #
of cpus automatically you can do:
cpus = system("exit `grep processor /proc/cpuinfo | wc -l`");
cpus = WEXITSTATUS(cpus);
and start as many threads as many CPUs there are in the system.
Ingo
next prev parent reply other threads:[~2008-01-16 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:37 Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon Colin Fowler
2008-01-14 18:55 ` Ingo Molnar
2008-01-14 22:42 ` Colin Fowler
2008-01-14 22:43 ` Colin Fowler
2008-01-15 17:01 ` Colin Fowler
2008-01-15 22:06 ` Ingo Molnar
2008-01-15 23:05 ` Colin Fowler
2008-01-16 15:35 ` Ingo Molnar
2008-01-16 16:10 ` Colin Fowler
2008-01-16 16:19 ` Ingo Molnar [this message]
2008-01-16 16:38 ` Colin Fowler
2008-01-16 17:34 ` Colin Fowler
2008-01-18 10:55 ` 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=20080116161951.GA15000@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=elethiomel@gmail.com \
--cc=linux-kernel@vger.kernel.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