mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, Chris Mason <clm@fb.com>,
	lkp@01.org, Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Davidlohr Bueso <dbueso@suse.de>, Hugh Dickins <hughd@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>,
	Mel Gorman <mgorman@techsingularity.net>,
	Darren Hart <dvhart@linux.intel.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Xiaolong Ye <xiaolong.ye@intel.com>
Subject: Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops
Date: Tue, 29 Mar 2016 09:39:57 +0200	[thread overview]
Message-ID: <20160329073957.GD3408@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <8737rkgr20.fsf@yhuang-dev.intel.com>

On Mon, Mar 21, 2016 at 04:42:47PM +0800, Huang, Ying wrote:
> OK.  We will try to improve on this side.  But it is not an easy task
> for us to provided easy to use simple binaries.  Do you think something
> like Docker image is easy to use?

Docker muck would just make me turn around and run.

      parent reply	other threads:[~2016-03-29  7:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29  8:36 kernel test robot
2016-02-29  9:37 ` Ingo Molnar
2016-02-29 17:37   ` Davidlohr Bueso
2016-03-01  8:38   ` [LKP] " Huang, Ying
2016-03-18  6:12   ` Huang, Ying
2016-03-18  8:35     ` Thomas Gleixner
2016-03-21  2:53       ` Huang, Ying
2016-03-21  8:00         ` Thomas Gleixner
2016-03-21  8:42           ` Huang, Ying
2016-03-28 17:14             ` Darren Hart
2016-03-29  1:12               ` Huang, Ying
2016-03-29  5:17                 ` Darren Hart
2016-03-29  5:57                   ` Huang, Ying
2016-03-29  7:39             ` Peter Zijlstra [this message]

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=20160329073957.GD3408@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bigeasy@linutronix.de \
    --cc=clm@fb.com \
    --cc=dbueso@suse.de \
    --cc=dvhart@linux.intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mgorman@suse.de \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xiaolong.ye@intel.com \
    --cc=ying.huang@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

Powered by JetHome