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] [day] [month] [year] [list]
Message-ID: <20210406124126.GM17806@zn.tnic>
Date:   Tue, 6 Apr 2021 14:41:26 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
        LKML <linux-kernel@...r.kernel.org>, Song Liu <song@...nel.org>,
        linux-raid@...r.kernel.org, it+linux-x86@...gen.mpg.de,
        Krzysztof Olędzki <ole@....pl>,
        Andy Lutomirski <luto@...nel.org>,
        Krzysztof Mazur <krzysiek@...lesie.net>
Subject: Re: [regression 5.4.97 → 5.10.24]: raid6 avx2x4 speed drops from 18429 MB/s to 6155 MB/s

On Tue, Apr 06, 2021 at 12:58:15PM +0200, Paul Menzel wrote:
> I booted Linux 5.12-rc6, containing these commits, on a Dell OptiPlex 5055
> with AMD Ryzen 5 PRO 1500 Quad-Core Processor, and the regression is still
> present for `avx2x4 xor()`:

So I don't think that's a regression - this looks more like "you should
not look at those numbers and compare them". Below are some results from
boot logs on one of my test boxes, first column is the kernel version.

IOW, you can use those numbers as a random number generator.

Now, I'm not saying that there isn't anything happening after
5.4-5.6-ish timeframe but this needs to be checked with a proper
benchmark and then look at what could be causing this. It could be the
MXCSR clearing but it's not like we don't need that so there won't be a
whole lot we can do.

But someone would have to sit down and do proper measurements first. And
bisect. Then we'll see...

HTH.

01-0+   :raid6: avx2x4   xor() 10311 MB/s
01-rc3+ :raid6: avx2x4   xor()  5497 MB/s
01-rc6+ :raid6: avx2x4   xor()  5369 MB/s
02-rc3+ :raid6: avx2x4   xor()  9812 MB/s
02-rc5+ :raid6: avx2x4   xor() 11479 MB/s
03-rc1+ :raid6: avx2x4   xor()  6434 MB/s
03-rc2+ :raid6: avx2x4   xor()  5487 MB/s
03-rc3+ :raid6: avx2x4   xor()  4840 MB/s
03-rc5+ :raid6: avx2x4   xor() 11104 MB/s
04-rc1+ :raid6: avx2x4   xor()  6443 MB/s
04-rc2+ :raid6: avx2x4   xor()  4959 MB/s
04-rc3+ :raid6: avx2x4   xor()  4918 MB/s
04-rc7+ :raid6: avx2x4   xor()  5219 MB/s
05-rc1+ :raid6: avx2x4   xor()  5362 MB/s
05-rc2+ :raid6: avx2x4   xor()  5356 MB/s
05-rc7+ :raid6: avx2x4   xor()  5821 MB/s
06-rc1+ :raid6: avx2x4   xor()  3358 MB/s
06-rc2+ :raid6: avx2x4   xor()  3591 MB/s
06-rc4+ :raid6: avx2x4   xor()  3947 MB/s
06-rc6+ :raid6: avx2x4   xor()  4100 MB/s
06-rc7+ :raid6: avx2x4   xor()  4038 MB/s
07-0+   :raid6: avx2x4   xor()  3410 MB/s
07-rc1+ :raid6: avx2x4   xor()  4836 MB/s
07-rc2+ :raid6: avx2x4   xor()  3194 MB/s
07-rc5  :raid6: avx2x4   xor()  4220 MB/s
07-rc6+ :raid6: avx2x4   xor()  3949 MB/s
07-rc7+ :raid6: avx2x4   xor()  3238 MB/s
09-0+   :raid6: avx2x4   xor()  3259 MB/s
09-rc1+ :raid6: avx2x4   xor()  2963 MB/s
09-rc4+ :raid6: avx2x4   xor()  2593 MB/s
09-rc5+ :raid6: avx2x4   xor()  2555 MB/s
09-rc7+ :raid6: avx2x4   xor()  3333 MB/s
09-rc8+ :raid6: avx2x4   xor()  2979 MB/s
10-rc4+ :raid6: avx2x4   xor()  4482 MB/s
10-rc5+ :raid6: avx2x4   xor()  6170 MB/s
10-rc7+ :raid6: avx2x4   xor()  3557 MB/s
11-rc1+ :raid6: avx2x4   xor()  1461 MB/s
11-rc2+ :raid6: avx2x4   xor()  4095 MB/s
11-rc7+ :raid6: avx2x4   xor()  6088 MB/s
12-rc1+ :raid6: avx2x4   xor()  4147 MB/s
12-rc2+ :raid6: avx2x4   xor()  4361 MB/s
12-rc3+ :raid6: avx2x4   xor()  4070 MB/s
12-rc4+ :raid6: avx2x4   xor()  6078 MB/s

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ