Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: akpm@linux-foundation.org, linux-raid@vger.kernel.org,
	linux-crypto@vger.kernel.org, x86@kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Richard Weinberger <richard@nod.at>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 0/3] lib/raid: opt out of initializing MXCSR and 387 state
Date: Thu, 12 Nov 2026 14:40:36 +0100	[thread overview]
Message-ID: <20261112134036.GA23216@lst.de> (raw)
In-Reply-To: <20261111205604.47547-1-ebiggers@kernel.org>

On Wed, Nov 11, 2026 at 12:56:01PM -0800, Eric Biggers wrote:
> This series slightly reduces the overhead of the x86 kernel-mode "FPU"
> sections in the RAID code by using kernel_fpu_begin_mask(0) instead of
> kernel_fpu_begin(), thus opting out of the 'ldmxcsr' (and on 32-bit
> kernels, also 'fninit').  MXCSR is irrelevant for integer code.

Maybe we really want a kernel_avx_{begin,end} after all :)

I'd still prefer that, but in the meantime the change looks fine:

Reviewed-by: Christoph Hellwig <hch@lst.de>


      parent reply	other threads:[~2026-11-12 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 20:56 [PATCH 0/3] lib/raid: opt out of initializing MXCSR and 387 state Eric Biggers
2026-11-11 20:56 ` [PATCH 1/3] um: Define kernel_fpu_begin_mask() Eric Biggers
2026-11-12  7:28   ` Johannes Berg
2026-11-11 20:56 ` [PATCH 2/3] xor: opt out of initializing MXCSR and 387 state Eric Biggers
2026-11-11 20:56 ` [PATCH 3/3] raid6: " Eric Biggers
2026-11-12 13:40 ` Christoph Hellwig [this message]

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=20261112134036.GA23216@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=ebiggers@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=richard@nod.at \
    --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