2015-02-03 07:45:13

by kernel test robot

[permalink] [raw]
Subject: [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops

_______________________________________________
LKP mailing list
[email protected]


Attachments:
job.yaml (1.71 kB)
reproduce (31.00 B)
(No filename) (86.00 B)
Download all attachments

2015-02-03 10:27:54

by Will Deacon

[permalink] [raw]
Subject: Re: [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops

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.

Will

2015-02-05 05:41:55

by kernel test robot

[permalink] [raw]
Subject: Re: [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops

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.

Best Regards,
Huang, Ying

2015-02-12 04:56:35

by Huang, Ying

[permalink] [raw]
Subject: Re: [LKP] [mm] 721c21c17ab: +11.7% will-it-scale.per_thread_ops

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