linux-kernel - Re: [LKP] Re: [mm/gup] a308c71bf1: stress-ng.vm-splice.ops_per

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dd22f78e-764b-4896-e2d0-5f4e4cf178af@linux.intel.com>
Date:   Thu, 5 Nov 2020 16:28:54 +0800
From:   Xing Zhengjun <zhengjun.xing@...ux.intel.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        kernel test robot <rong.a.chen@...el.com>,
        Jann Horn <jannh@...gle.com>
Cc:     Peter Xu <peterx@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
        lkp@...ts.01.org, kernel test robot <lkp@...el.com>,
        zhengjun.xing@...el.com
Subject: Re: [LKP] Re: [mm/gup] a308c71bf1: stress-ng.vm-splice.ops_per_sec
 -95.6% regression



On 11/5/2020 2:29 AM, Linus Torvalds wrote:
> On Mon, Nov 2, 2020 at 1:15 AM kernel test robot <rong.a.chen@...el.com> wrote:
>>
>> Greeting,
>>
>> FYI, we noticed a -95.6% regression of stress-ng.vm-splice.ops_per_sec due to commit:
>>
>> commit: a308c71bf1e6e19cc2e4ced31853ee0fc7cb439a ("mm/gup: Remove enfornced COW mechanism")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> Note that this is just the reverse of the previous 2000% improvement
> reported by the test robot here:
> 
>      https://lore.kernel.org/lkml/20200611040453.GK12456@shao2-debian/
> 
> and the explanation seems to remain the same:
> 
>      https://lore.kernel.org/lkml/CAG48ez1v1b4X5LgFya6nvi33-TWwqna_dc5jGFVosqQhdn_Nkg@mail.gmail.com/
> 
> IOW, this is testing a special case (zero page lookup) that the "force
> COW" patches happened to turn into a regular case (COW creating a
> regular page from the zero page).
> 
> The question is whether we should care about the zero page for gup_fast lookup.
> 
> If we do care, then the proper fix is likely simply to allow the zero
> page in fast-gup, the same way we already do in slow-gup.
> 
> ENTIRELY UNTESTED PATCH ATTACHED.
> 
> Rong - mind testing this? I don't think the zero-page _should_ be
> something that real loads care about, but hey, maybe people do want to
> do things like splice zeroes very efficiently..

I test the patch, the regression still existed.

=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/nr_threads/disk/testtime/class/cpufreq_governor/ucode:
 
lkp-csl-2sp5/stress-ng/debian-10.4-x86_64-20200603.cgz/x86_64-rhel-8.3/gcc-9/100%/1HDD/30s/pipe/performance/0x5002f01

commit:
   1a0cf26323c80e2f1c58fc04f15686de61bfab0c
   a308c71bf1e6e19cc2e4ced31853ee0fc7cb439a
   da5ba9980aa2211c1e2a89fc814abab2fea6f69d (debug patch)

1a0cf26323c80e2f a308c71bf1e6e19cc2e4ced3185 da5ba9980aa2211c1e2a89fc814
---------------- --------------------------- ---------------------------
          %stddev     %change         %stddev     %change         %stddev
              \          |                \          |                \
  3.406e+09           -95.6%   1.49e+08           -96.4%  1.213e+08 
    stress-ng.vm-splice.ops
  1.135e+08           -95.6%    4965911           -96.4%    4041777 
    stress-ng.vm-splice.ops_per_sec

> 
> And note the "untested" part of the patch. It _looks_ fairly obvious,
> but maybe I'm missing something.
> 
>              Linus
> 
> 
> _______________________________________________
> LKP mailing list -- lkp@...ts.01.org
> To unsubscribe send an email to lkp-leave@...ts.01.org
> 

-- 
Zhengjun Xing