From: Mike Galbraith <bitbucket@online.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: sched: context tracking demolishes pipe-test
Date: Mon, 01 Jul 2013 11:20:32 +0200 [thread overview]
Message-ID: <1372670432.7678.114.camel@marge.simpson.net> (raw)
In-Reply-To: <1372669941.7678.113.camel@marge.simpson.net>
On Mon, 2013-07-01 at 11:12 +0200, Mike Galbraith wrote:
> On Mon, 2013-07-01 at 10:06 +0200, Peter Zijlstra wrote:
>
> > So aside from the context tracking stuff, there's still a regression
> > we might want to look at. That's still a ~10% drop against 2.6.32 for
> > TCP_RR and few percents for tbench.
>
> Yeah, known, and some of it's ours.
(btw tbench has a ~5% phase-of-moon jitter, you can pretty much
disregard that one)
next prev parent reply other threads:[~2013-07-01 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 7:57 sched: context tracking demolishes pipe-test Mike Galbraith
2013-06-30 21:29 ` Peter Zijlstra
2013-07-01 6:07 ` Mike Galbraith
2013-07-01 8:06 ` Peter Zijlstra
2013-07-01 9:12 ` Mike Galbraith
2013-07-01 9:20 ` Mike Galbraith [this message]
2013-07-02 4:03 ` Mike Galbraith
2013-07-02 7:19 ` Mike Galbraith
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=1372670432.7678.114.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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