From: Mike Galbraith <efault@gmx.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Subject: Re: tbench regression with 2.6.33-rc1
Date: Tue, 29 Dec 2009 06:49:05 +0100 [thread overview]
Message-ID: <1262065745.17082.0.camel@marge.simson.net> (raw)
In-Reply-To: <1262063959.13697.6.camel@minggr.sh.intel.com>
On Tue, 2009-12-29 at 13:19 +0800, Lin Ming wrote:
> On Tue, 2009-12-29 at 13:24 +0800, Mike Galbraith wrote:
> > On Tue, 2009-12-29 at 10:09 +0800, Lin Ming wrote:
> > > And also no regression if I run tbench with RT scheduler on tulsa
> > > machine, as below command,
> > >
> > > schedtool -R -p 20 -e tbench_srv &
> > > schedtool -R -p 20 -e tbench 32
> >
> > Hm, odd. I'd expect tbench to suffer when run SCHED_RR, and here it
> > does, achieving roughly 85% of lowest SCHED_OTHER throughput.
>
> Here is some misunderstanding.
> I compared SCHED_RR tbench with 2.6.32 and 2.6.33-rc1 and no regression
> found.
>
> For the same kernel, SCHED_RR tbench only achieved ~40% of SCHED_OTHER
> throughput.
Ah. Thanks for the clarification.
-Mike
next prev parent reply other threads:[~2009-12-29 5:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 11:11 tbench regression with 2.6.33-rc1 Lin Ming
2009-12-27 8:32 ` Mike Galbraith
2009-12-27 8:59 ` Peter Zijlstra
2009-12-27 9:41 ` Mike Galbraith
2009-12-27 10:11 ` Peter Zijlstra
2010-01-02 3:56 ` Frederic Weisbecker
2009-12-29 2:09 ` Lin Ming
2009-12-29 5:24 ` Mike Galbraith
2009-12-29 5:19 ` Lin Ming
2009-12-29 5:49 ` Mike Galbraith [this message]
2010-01-06 6:01 ` Mike Galbraith
2010-01-06 5:55 ` Lin Ming
2010-01-06 6:52 ` Lin Ming
2010-01-06 7:44 ` Mike Galbraith
2010-01-11 12:08 ` Peter Zijlstra
2010-01-11 16:16 ` Mike Galbraith
2010-01-12 1:09 ` Lin Ming
2010-01-12 2:33 ` Mike Galbraith
2010-01-12 3:13 ` Lin Ming
2010-01-12 4:14 ` Mike Galbraith
2010-01-12 8:54 ` Peter Zijlstra
2010-01-12 9:20 ` Lin Ming
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=1262065745.17082.0.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yanmin_zhang@linux.intel.com \
/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