From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>, Christoph Hellwig <hch@lst.de>,
Demian Shulhan <demyansh@gmail.com>
Subject: Re: [PATCH 0/2] raid6/arm64: Use aggregation and 3-way XOR
Date: Thu, 19 Nov 2026 14:50:41 -0800 [thread overview]
Message-ID: <20261119225041.GD1894@quark> (raw)
In-Reply-To: <20261118183335.1944213-4-ardb+git@google.com>
On Wed, Nov 18, 2026 at 07:33:36PM +0100, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> Tweak the arm64/ARM P/Q gen/xor code to use 3-way XOR instructions where
> available. Details are in the commit logs.
>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Eric Biggers <ebiggers@kernel.org>
> Cc: Demian Shulhan <demyansh@gmail.com>
>
> Ard Biesheuvel (2):
> raid6: neon: process four data disks per Horner step
> raid6: arm64: use the EOR3 instruction where available
I left some minor comments, and I don't know this code very well. But
overall this looks good.
Acked-by: Eric Biggers <ebiggers@kernel.org>
linux-raid@vger.kernel.org is supposed to be Cc'ed on lib/raid/ changes.
(Though I don't know whether anyone from there pays attention to these.)
Andrew Morton has been taking lib/raid/ changes for now, so you should
Cc him too unless you're trying to get someone else to take these.
- Eric
prev parent reply other threads:[~2026-11-19 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 18:33 [PATCH 0/2] raid6/arm64: Use aggregation and 3-way XOR Ard Biesheuvel
2026-11-18 18:33 ` [PATCH 1/2] raid6: neon: process four data disks per Horner step Ard Biesheuvel
2026-11-19 22:44 ` Eric Biggers
2026-11-18 18:33 ` [PATCH 2/2] raid6: arm64: use the EOR3 instruction where available Ard Biesheuvel
2026-11-19 22:35 ` Eric Biggers
2026-11-19 22:50 ` Eric Biggers [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=20261119225041.GD1894@quark \
--to=ebiggers@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=demyansh@gmail.com \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.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