From: Darren Hart <dvhart@infradead.org>
To: lkp@lists.01.org
Subject: Re: [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops
Date: Wed, 29 Oct 2014 21:39:18 -0700 [thread overview]
Message-ID: <20141030043918.GK14609@vmdeb7> (raw)
In-Reply-To: <20141027021822.GH27038@yliu-dev.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
On Mon, Oct 27, 2014 at 10:18:22AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure get_futex_key_refs() always implies a barrier")
Wow, this is great information to get for free. Thanks Fengguang!
--
Darren Hart
Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@infradead.org>
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: Wed, 29 Oct 2014 21:39:18 -0700 [thread overview]
Message-ID: <20141030043918.GK14609@vmdeb7> (raw)
In-Reply-To: <20141027021822.GH27038@yliu-dev.sh.intel.com>
On Mon, Oct 27, 2014 at 10:18:22AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure get_futex_key_refs() always implies a barrier")
Wow, this is great information to get for free. Thanks Fengguang!
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-10-30 4:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 2:18 [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops kernel test robot
2014-10-27 2:18 ` [LKP] " kernel test robot
2014-10-27 2:26 ` Davidlohr Bueso
2014-10-27 2:26 ` [LKP] " Davidlohr Bueso
2014-10-30 4:39 ` Darren Hart [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=20141030043918.GK14609@vmdeb7 \
--to=dvhart@infradead.org \
--cc=lkp@lists.01.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 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.