From: Ingo Molnar <mingo@elte.hu>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
tglx@linutronix.de, oleg@redhat.com,
linux-kernel@vger.kernel.org, seto.hidetoshi@jp.fujitsu.com,
ming.m.lin@intel.com
Subject: Re: [PATCH 0/2] fix the itimer regression (BZ 12618)
Date: Fri, 6 Feb 2009 16:18:32 +0100 [thread overview]
Message-ID: <20090206151832.GL18368@elte.hu> (raw)
In-Reply-To: <1233895919.2604.323.camel@ymzhang>
* Zhang, Yanmin <yanmin_zhang@linux.intel.com> wrote:
> On Thu, 2009-02-05 at 13:06 +0100, Ingo Molnar wrote:
> > * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > > This should hopefully address all the itimer borkage.
> >
> > Applied to tip:timers/urgent, thanks Peter!
> >
> > Yanmin: could you check hacbench_pth with latest tip/master, do
> > these fixes resolve that 3% regression you reported?
>
> Lin Ming tested it and hackbench_pth/volanoMark regression all disappear.
> But oltp has a regression. We think oltp new regression isn't related to
> the patch. Ming is investigating it.
Potential suspects for oltp regression would be:
3d39870: sched_rt: don't use first_cpu on cpumask created with cpumask_and
a571bbe: sched: fix buddie group latency
a9f3e2b: sched: clear buddies more aggressively
1596e29: sched: symmetric sync vs avg_overlap
d942fb6: sched: fix sync wakeups
Ingo
next prev parent reply other threads:[~2009-02-06 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 11:24 [PATCH 0/2] fix the itimer regression (BZ 12618) Peter Zijlstra
2009-02-05 11:24 ` [PATCH 1/2] signal: re-add dead task accumulation stats Peter Zijlstra
2009-02-05 11:24 ` [PATCH 2/2] timers: split process wide cpu clocks/timers Peter Zijlstra
2009-02-05 21:30 ` Oleg Nesterov
2009-02-05 22:20 ` Peter Zijlstra
2009-02-05 12:06 ` [PATCH 0/2] fix the itimer regression (BZ 12618) Ingo Molnar
2009-02-06 4:51 ` Zhang, Yanmin
2009-02-06 15:18 ` Ingo Molnar [this message]
2009-02-09 6:46 ` Lin Ming
2009-02-09 21:47 ` Ingo Molnar
2009-02-10 5:52 ` Mike Galbraith
2009-02-10 12:47 ` Peter Zijlstra
2009-02-11 2:09 ` Zhang, Yanmin
2009-02-12 11:05 ` Ingo Molnar
2009-02-13 9:15 ` Lin Ming
2009-02-13 10:06 ` Ingo Molnar
2009-02-11 13:11 ` Ingo Molnar
2009-02-11 13:27 ` Peter Zijlstra
2009-02-10 2:48 ` Lin Ming
2009-02-11 12:59 ` 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=20090206151832.GL18368@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=oleg@redhat.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.