From: Davidlohr Bueso <dave@stgolabs.net>
To: kernel test robot <fengguang.wu@intel.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: Re: [LKP] [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops
Date: Sun, 26 Oct 2014 19:26:01 -0700 [thread overview]
Message-ID: <1414376761.12733.13.camel@linux-t7sj.site> (raw)
In-Reply-To: <20141027021822.GH27038@yliu-dev.sh.intel.com>
On Mon, 2014-10-27 at 10:18 +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure get_futex_key_refs() always implies a barrier")
fwiw I was also able to reproduce similar results, with the hashing
costing (unsurprisingly) around an extra ~10% with the new barrier, not
much we can do about that. In any case these are pretty low level
measurements so shouldn't impact too much. Additionally, any user that
cares about performance will try to avoid incurring futex calls into
kernel space.
next prev parent reply other threads:[~2014-10-27 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 2:18 [LKP] [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops kernel test robot
2014-10-27 2:26 ` Davidlohr Bueso [this message]
2014-10-30 4:39 ` Darren Hart
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=1414376761.12733.13.camel@linux-t7sj.site \
--to=dave@stgolabs.net \
--cc=catalin.marinas@arm.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=yuanhan.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox