From: Andi Kleen <andi@firstfloor.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, linux-kernel@vger.kernel.org, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, andi@firstfloor.org,
kan.liang@linux.intel.com, lkp@lists.01.org
Subject: Re: [perf] 06e0dbcfd3: phoronix-test-suite.mbw.0.mib_s 12.6% improvement
Date: Sun, 27 Oct 2019 09:32:50 -0700 [thread overview]
Message-ID: <20191027163248.nv63uybzjstoigj5@two.firstfloor.org> (raw)
In-Reply-To: <20191027051812.GJ29418@shao2-debian>
On Sun, Oct 27, 2019 at 01:18:12PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a 12.6% improvement of phoronix-test-suite.mbw.0.mib_s due to commit:
Wow! Sadly it's a false positive, from lowering perf overhead, instead
of improving the workload. Still seems like a good thing.
Note that there is a perf user tool change coming soon that will likely
improve it even more (using affiity to optimize all perf IPIs).
-Andi
next prev parent reply other threads:[~2019-10-27 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 9:20 [PATCH 0/3] Various optimizations for event creation Peter Zijlstra
2019-10-22 9:20 ` [PATCH 1/3] perf: Optimize perf_install_in_event() Peter Zijlstra
2019-10-22 10:03 ` Peter Zijlstra
2019-10-23 12:30 ` Alexander Shishkin
2019-10-23 13:44 ` Peter Zijlstra
2019-10-23 14:08 ` Peter Zijlstra
2019-10-22 9:20 ` [PATCH 2/3] perf: Optimize perf_init_event() Peter Zijlstra
2019-10-27 5:18 ` [perf] 06e0dbcfd3: phoronix-test-suite.mbw.0.mib_s 12.6% improvement kernel test robot
2019-10-27 16:32 ` Andi Kleen [this message]
2019-10-22 9:20 ` [PATCH 3/3] perf: Optimize perf_init_event() for TYPE_SOFTWARE Peter Zijlstra
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=20191027163248.nv63uybzjstoigj5@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rong.a.chen@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®