From: Miroslav Cimerman <mc@raidlab.org>
To: song@kernel.org, yukuai@fygo.io, akpm@linux-foundation.org
Cc: ardb@kernel.org, ebiggers@kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
magiclinan@didiglobal.com, xiao@kernel.org,
antosha20xx@gmail.com
Subject: Re: [PATCH] raid6: use normal stores in the x86 x4 xor_syndrome functions
Date: Thu, 12 Nov 2026 13:21:27 +0100 [thread overview]
Message-ID: <20261112122127.190285-2-mc@raidlab.org> (raw)
In-Reply-To: <20261109030805.25709-1-mc@raidlab.org>
Anton Gavriliuk tested the patch on Zen 5 (thread "xor_gen() md-raid6
performance improvement"):
HPE DL345 Gen11, AMD EPYC 9455, 6x PCIe 5.0 NVMe (CM7-V 3.2 TB),
Fedora 45 config, v7.4-rc2 with and without the patch, both kernels
select avx512x4. RAID-6 4+2, chunk 512K, no bitmap, rmw_level=2,
fio 4k randwrite, O_DIRECT, io_uring, 60 s, 3 runs per kernel:
md defaults, 1 job x QD64:
without 127k / 122k / 125k IOPS (mean 124.7k)
with 132k / 139k / 137k IOPS (mean 136.0k) +9.1%
(a repeat run a day later: 127k without, 135k with)
group_thread_cnt=8, stripe_cache_size=32768, 16 jobs x QD64:
without 467k / 468k / 470k IOPS (mean 468.3k)
with 473k / 471k / 471k IOPS (mean 471.7k) +0.7%
With md's defaults one md thread does the stripe work for all writes
and is busy most of the time (about 80% in top), so a cheaper
xor_syndrome() shows up in IOPS. With 8 workers per node the limit is
lock contention in md instead (on my machine most of the time goes to
spinning on device_lock), so the saving hardly shows.
Miroslav
next prev parent reply other threads:[~2026-11-12 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 3:08 [PATCH] raid6: use normal stores in the x86 x4 xor_syndrome functions Miroslav Cimerman
2026-11-12 12:21 ` Miroslav Cimerman [this message]
2026-11-12 12:33 ` Anton Gavriliuk
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=20261112122127.190285-2-mc@raidlab.org \
--to=mc@raidlab.org \
--cc=akpm@linux-foundation.org \
--cc=antosha20xx@gmail.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
--cc=yukuai@fygo.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.