From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: x86@kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, ardb@kernel.org,
greearb@candelatech.com, shaw.leon@gmail.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
luto@kernel.org, Jason@zx2c4.com
Subject: Re: [RFC PATCH 0/2] Eliminate the no-SIMD en/decryption fallbacks on x86
Date: Fri, 21 Feb 2025 11:53:48 +0800 [thread overview]
Message-ID: <Z7f4zNVoVB1jamIP@gondor.apana.org.au> (raw)
In-Reply-To: <20250220051325.340691-1-ebiggers@kernel.org>
Eric Biggers <ebiggers@kernel.org> wrote:
> The patchset can also be retrieved from:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git x86-softirq-fpu-fix-v1
>
> This patchset fixes a longstanding issue where kernel-mode FPU (i.e.,
> SIMD) was not reliably usable in softirqs in x86, which was creating the
> need for a fallback. The fallback was really bad for performance, and
> it even hurt performance for users that never encountered the edge case
> where kernel-mode FPU was not usable.
Great work!
> I also benchmarked bidirectional IPsec, which has been claimed to often
> hit the edge case where kernel-mode FPU was previously not usable in
> softirq context. Ultimately, I was not actually able to reproduce that
> edge case being reached unless I reduced the number of CPUs to 1, in
> which case it then started being occasionally reached. Regardless, even
> without that case being reached, IPsec throughput still improved by 2%.
> In situations where that case was being reached, or where users required
> a synchronous algorithm, a much larger improvement should be seen.
You would need a situation where your CPU is maxed out by your
bandwidth, so on a physical box these days you would need 10GbE
at the minimum.
However, I used to be able to easily reproduce this using virtualisation
because there the bandwidth is essentially unlimited. So perhaps
a KVM guest with a single CPU doing bidirection IPsec to the host
should be enough to reproduce this case.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2025-02-21 3:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 5:13 [RFC PATCH 0/2] Eliminate the no-SIMD en/decryption fallbacks on x86 Eric Biggers
2025-02-20 5:13 ` [RFC PATCH 1/2] x86/fpu: make kernel-mode FPU reliably usable in softirqs Eric Biggers
2025-02-21 7:38 ` Xiao Liang
2025-02-21 19:31 ` Eric Biggers
2025-02-25 22:21 ` David Laight
2025-02-25 22:59 ` Eric Biggers
2025-02-26 17:09 ` Dave Hansen
2025-02-28 3:59 ` Eric Biggers
2025-02-28 12:39 ` Ard Biesheuvel
2025-02-20 5:13 ` [RFC PATCH 2/2] crypto: x86 - stop using the SIMD helper Eric Biggers
2025-02-21 3:53 ` Herbert Xu [this message]
2025-02-24 18:57 ` [RFC PATCH 0/2] Eliminate the no-SIMD en/decryption fallbacks on x86 Eric Biggers
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=Z7f4zNVoVB1jamIP@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=greearb@candelatech.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=shaw.leon@gmail.com \
--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