All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression
Date: Thu, 12 Apr 2018 09:12:35 +0800	[thread overview]
Message-ID: <20180412011235.GH17893@yexl-desktop> (raw)
In-Reply-To: <CAAmzW4MHjvDrDdoeSf3imjRboCA+Z4yTaDF=WsS3vsjYUCiVUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4091 bytes --]

On 04/09, Joonsoo Kim wrote:
>2018-04-09 14:56 GMT+09:00 Ye Xiaolong <xiaolong.ye@intel.com>:
>> On 04/05, Joonsoo Kim wrote:
>>>I may find the reason of this regression. Could you test this patch on
>>>top of this patchset?
>>>
>>>http://lkml.kernel.org/r/<1522913236-15776-1-git-send-email-iamjoonsoo.kim@lge.com>
>>
>> It'd be better if you can provide your repo for this fix patch, it's more
>> convenient for 0day to verify it.
>
>Okay! Could you check following git tree and branch to fix the
>reported regression?
>
>https://github.com/JoonsooKim/linux.git cma-fixup-thp-next-20180403
>
>Related commits are:
>f11152b mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving
>b2adb03 Revert "Revert "mm/cma: manage the memory of the CMA area by
>using the ZONE_MOVABLE""
>76148e2 Revert "Revert "mm/page_alloc: don't reserve ZONE_HIGHMEM for
>ZONE_MOVABLE request""
>
>Base commit is '76148e2' and this regression happens on 'b2adb03'.
>Fix is commit 'f11152b'.

Sorry for the late, below is the comparison of commit f6572f9cd248df2c, 2b0f904a5a,
and fix commit f11152b, seems it doesn't help to recover the performance.


$ compare -at f6572f9cd248df2cbcfc78088ff3b36f5a9c5bd6 2b0f904a5a f11152bc91ec97cd3c3f710f9bd0b0bbedbef7b4 -g fio-basic
tests: 1
testcase/path_params/tbox_group/run: fio-basic/2pmem-ext4-200s-50%-tb-randread-2M-mmap-200G-performance/lkp-hsw-ep6

f6572f9cd248df2c  2b0f904a5a8781498417d67226  f11152bc91ec97cd3c3f710f9b  
----------------  --------------------------  --------------------------  
         %stddev      change         %stddev      change         %stddev
             \          |                \          |                \  
     11462             -16%       9605             -18%       9371        fio.read_bw_MBps
      5731             -16%       4802             -18%       4685        fio.read_iops
      0.46 ± 22%       211%       1.45 ±  4%       207%       1.43 ±  4%  fio.latency_50ms%
      0.04 ± 11%       111%       0.09 ±  8%       163%       0.11 ±  9%  fio.latency_2ms%
      7.75 ±  4%       160%      20.15             161%      20.25        fio.latency_20ms%
      0.29 ±  6%        41%       0.40 ±  3%        45%       0.42 ±  8%  fio.latency_1000us%
     15720 ±  7%        44%      22592              43%      22464        fio.read_clat_99%_us
     10544              33%      14048              34%      14112        fio.read_clat_95%_us
      9792              32%      12896              32%      12896        fio.read_clat_90%_us
   1811975              24%    2254706              27%    2304726        fio.time.maximum_resident_set_size
      4880              19%       5825              22%       5970        fio.read_clat_mean_us
      0.29 ± 14%        17%       0.33 ±  3%        20%       0.34 ±  5%  fio.latency_500us%
     19.32 ±  4%       -24%      14.69 ±  3%        16%      22.37 ±  4%  fio.latency_10ms%
     10723 ±  4%                 10867 ±  3%         9%      11738 ±  4%  fio.read_clat_stddev
     24578              10%      26917               6%      26075        fio.time.voluntary_context_switches
       518             -17%        430              -5%        493        fio.time.user_time
 5.754e+08             -16%  4.806e+08             -18%  4.691e+08        fio.time.major_page_faults
 4.603e+09             -16%  3.845e+09             -18%  3.753e+09        fio.time.file_system_inputs
     70.42             -13%      61.36             -24%      53.64        fio.latency_4ms%
  54585366             -15%   46353339             -19%   44289507        interrupts.CAL:Function_call_interrupts
    318043             -12%     278980             -15%     269034        vmstat.system.in
  10914641             -17%    9111830             -18%    8913838        vmstat.io.bi
    349206 ±  3%        -9%     319016 ±  3%         8%     377455 ±  6%  softirqs.RCU
   4263579                     4289700             -14%    3676822        softirqs.TIMER

Thanks,
Xiaolong


>
>Thanks.

  parent reply	other threads:[~2018-04-12  1:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02  6:35 [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression kernel test robot
2018-01-02  6:35 ` kernel test robot
2018-01-03  2:05 ` Joonsoo Kim
2018-01-03  2:05   ` Joonsoo Kim
2018-01-06  9:26   ` Ye Xiaolong
2018-01-06  9:26     ` Ye Xiaolong
2018-01-09  7:16     ` Joonsoo Kim
2018-01-09  7:16       ` Joonsoo Kim
2018-04-05  7:48       ` Joonsoo Kim
2018-04-05  7:48         ` Joonsoo Kim
2018-04-09  5:56         ` Ye Xiaolong
2018-04-09  7:25           ` Joonsoo Kim
2018-04-09  7:40             ` Ye Xiaolong
2018-04-12  1:12             ` Ye Xiaolong [this message]
2018-04-12  1:26               ` Joonsoo Kim
2018-04-13  1:18                 ` Ye Xiaolong
2018-04-23  6:39                   ` Joonsoo Kim
2018-05-03  4:46                     ` Ye Xiaolong

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=20180412011235.GH17893@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --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.