mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@tmb.nu>
To: Borislav Petkov <bp@alien8.de>, Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Song Liu <song@kernel.org>,
	linux-raid@vger.kernel.org, it+linux-x86@molgen.mpg.de
Subject: Re: [regression 5.4.97 → 5.10.24]: raid6 avx2x4 speed drops from 18429 MB/s to 6155 MB/s
Date: Sat, 03 Apr 2021 12:49:32 +0000	[thread overview]
Message-ID: <42011184-de0b-25d1-534f-a0d412d287a2@tmb.nu> (raw)

Den 2021-04-02 kl. 17:05, skrev Borislav Petkov:
> On Fri, Apr 02, 2021 at 10:33:51AM +0200, Paul Menzel wrote:
>> Dear Linux folks,
>>
>>
>> On an two socket AMD EPYC 7601, we noticed a decrease in raid6 avx2x4 speed
>> shown at the beginning of the boot.
>>
>>                         5.4.95        5.10.24
>> ----------------------------------------------
>> raid6: avx2x4 gen()   18429 MB/s     6155 MB/s
>> raid6: avx2x4 xor()    6644 MB/s     4274 MB/s
>> raid6: avx2x2 gen()   17894 MB/s    18744 MB/s
>> raid6: avx2x2 xor()   11642 MB/s    11950 MB/s
>> raid6: avx2x1 gen()   13992 MB/s    17112 MB/s
>> raid6: avx2x1 xor()   10855 MB/s    11143 MB/s
>
> Looks like those two might help:
>

That would mean only this is missing:
> 49200d17d27d x86/fpu/64: Don't FNINIT in kernel_fpu_begin()


as this one landed in 5.10.11:
> e45122893a98 x86/fpu: Add kernel_fpu_begin_mask() to selectively initialize state
>

--
Thomas


             reply	other threads:[~2021-04-03 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 12:49 Thomas Backlund [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-02  8:33 Paul Menzel
2021-04-02 14:05 ` Borislav Petkov
2021-04-06 10:58   ` Paul Menzel
2021-04-06 12:41     ` Borislav Petkov

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=42011184-de0b-25d1-534f-a0d412d287a2@tmb.nu \
    --to=tmb@tmb.nu \
    --cc=bp@alien8.de \
    --cc=it+linux-x86@molgen.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=song@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®