public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Will Deacon <will.deacon@arm.com>
Cc: LKP ML <lkp@01.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops
Date: Thu, 12 Feb 2015 12:56:31 +0800	[thread overview]
Message-ID: <1423716991.5968.125.camel@intel.com> (raw)
In-Reply-To: <1423114910.5968.9.camel@linux.intel.com>

On Thu, 2015-02-05 at 13:41 +0800, Huang Ying wrote:
> On Tue, 2015-02-03 at 10:27 +0000, Will Deacon wrote:
> > On Tue, Feb 03, 2015 at 07:45:04AM +0000, Huang Ying wrote:
> > > FYI, we noticed the below changes on
> > > 
> > > commit 721c21c17ab958abf19a8fc611c3bd4743680e38 ("mm: mmu_gather: use
> > > tlb->end != 0 only for TLB invalidation")
> > 
> > Is this delta relative to the previous commit, or something else? The
> > commit in question restored some 3.18 behaviour on task exit (namely
> > doing a fullmm TLB flush), so it would be interesting to know if you
> > see the same change against 3.18.
> 
> Sorry for late.  The delta is relative to the previous commit.  I will
> queue some test for 3.18 to check.

The test result for v3.18 compared with the commit 721c21c is as below.
You can find that the difference between v3.18 and 721c21c should be
less that between v3.18 and the previous commit (parent) for
will-it-scale.per_thread_ops.  I think this is expected.

testbox/testcase/testparams: nhm4/will-it-scale/performance-pread2

           v3.18  721c21c17ab958abf19a8fc611
----------------  --------------------------
         %stddev     %change         %stddev
             \          |                \  
  31541022 ±  0%     -12.2%   27698665 ±  0%  will-it-scale.time.voluntary_context_switches
   1079302 ±  0%      -6.3%    1011350 ±  2%  will-it-scale.per_process_ops
      0.04 ±  0%      -4.5%       0.03 ±  1%  will-it-scale.scalability
   1038581 ±  0%      -3.2%    1005724 ±  0%  will-it-scale.per_thread_ops

Best Regards,
Huang, Ying



      reply	other threads:[~2015-02-12  4:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  7:45 [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops Huang Ying
2015-02-03 10:27 ` Will Deacon
2015-02-05  5:41   ` Huang Ying
2015-02-12  4:56     ` Huang Ying [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=1423716991.5968.125.camel@intel.com \
    --to=ying.huang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.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