From: Lin Ming <ming.m.lin@intel.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <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, 12 Jan 2010 11:13:36 +0800 [thread overview]
Message-ID: <1263266016.3598.24.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1263263621.5905.6.camel@marge.simson.net>
On Tue, 2010-01-12 at 10:33 +0800, Mike Galbraith wrote:
> On Tue, 2010-01-12 at 09:09 +0800, Lin Ming wrote:
> > On Tue, 2010-01-12 at 00:16 +0800, Mike Galbraith wrote:
>
> > > I've been all through it too, same result. The below may make a bit of
> > > difference, but really has diddly spit to do with this oddity.
> >
> > I test this patch applied to 2.6.33-rc3, but no help on tbench
> > regression.
>
> Did you try it with the vmark fix also applied? I would have expected
> at least a _little_ improvement. (but then this regression _is_ a bit
> odd anyway)
I re-tested with both patches applied, but still no help.
BTW, why do you call that patch "vmark" fix? :)
I just wonder what "vmark" means.
Lin Ming
next prev parent reply other threads:[~2010-01-12 3:29 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
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 [this message]
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=1263266016.3598.24.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.