From: Mike Galbraith <efault@gmx.de>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: "Alex,Shi" <alex.shi@intel.com>,
ncrao@google.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
linux-kernel@vger.kernel.org, "Chen,
Tim C" <tim.c.chen@intel.com>,
zheng.z.yan@intel.com
Subject: Re: [performance bug] volanomark regression on 37-rc1
Date: Tue, 16 Nov 2010 08:26:36 -0700 [thread overview]
Message-ID: <1289921196.5169.176.camel@maggy.simson.net> (raw)
In-Reply-To: <AANLkTi=OK+B537S5D8H4=yV5zC8+RksnfYgoKsqEyk5+@mail.gmail.com>
On Tue, 2010-11-16 at 20:38 +0600, Rakib Mullick wrote:
> Does VolanoMark is used for scheduler benchmarking? If I'm not wrong,
> I don't think it directly relates to scheduler benchmarking.
It's not generally considered to be a wonderful benchmark, but it is a
good indicator, and worth keeping an eye on IMHO.
I don't recall whether that patch works with the idle testcase without
resetting the throttle, or if it's only a bit less effective. If it's
only a little less effective, I'd be inclined to just whack the reset as
Alex did. Whatever is done has to prevent high frequency balancing.
-Mike
next prev parent reply other threads:[~2010-11-16 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 9:34 Alex,Shi
2010-11-16 14:38 ` Rakib Mullick
2010-11-16 15:26 ` Mike Galbraith [this message]
2010-11-16 16:31 ` Nikhil Rao
2010-11-16 17:32 ` Mike Galbraith
2010-11-16 19:27 ` Nikhil Rao
2010-11-16 19:37 ` Peter Zijlstra
2010-11-17 1:17 ` Alex,Shi
[not found] ` <1290022924-3548-1-git-send-email-ncrao@google.com>
2010-11-17 19:45 ` Nikhil Rao
2010-11-18 14:08 ` [tip:sched/urgent] sched: Fix idle balancing tip-bot for Nikhil Rao
2010-11-18 14:08 ` [tip:sched/urgent] sched: Fix volanomark performance regression tip-bot for Alex Shi
2010-11-17 0:23 ` [performance bug] volanomark regression on 37-rc1 Alex,Shi
2010-11-16 16:21 ` Nikhil Rao
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=1289921196.5169.176.camel@maggy.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=alex.shi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ncrao@google.com \
--cc=rakib.mullick@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=zheng.z.yan@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
all inboxes | Powered by JetHome®