From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Jet Chen <jet.chen@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [cgroup] a0f9ec1f181: -4.3% will-it-scale.per_thread_ops
Date: Thu, 15 May 2014 09:11:17 +0200 [thread overview]
Message-ID: <1400137877.5175.147.camel@marge.simpson.net> (raw)
In-Reply-To: <20140515061422.GC5539@mtj.dyndns.org>
On Thu, 2014-05-15 at 02:14 -0400, Tejun Heo wrote:
> Hmmm... I'm completely stumped. The commit in question has nothing to
> do with tmpfs. It only affects three cgroup files - "tasks",
> "cgroup.procs" and "release_agent". It can't possibly have any effect
> on tmpfs operation. Maybe random effect through code alignment? Even
> that is highly unlikely.
Unlikely, but it happens. I bisected a tbench regression down to a
completely unrelated driver change, and watched it repeatably drop
throughput 5% despite skeptical "No way, show me that trick again".
-Mike
next prev parent reply other threads:[~2014-05-15 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 4:50 Jet Chen
2014-05-15 4:55 ` Tejun Heo
2014-05-15 6:00 ` Fengguang Wu
2014-05-15 6:14 ` Tejun Heo
2014-05-15 7:11 ` Mike Galbraith [this message]
2014-05-15 8:16 ` Fengguang Wu
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=1400137877.5175.147.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tj@kernel.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
Powered by JetHome