From: Christoph Hellwig <hch@infradead.org>
To: sunliming@linux.dev
Cc: Christoph Hellwig <hch@infradead.org>,
song@kernel.org, yukuai@fnnas.com, akpm@linux-foundation.org,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
sunliming <sunliming@kylinos.cn>
Subject: Re: [PATCH RESEND v3 2/3] lib/raid6: Optimizing the raid6_select_algo time through asynchronous processing
Date: Tue, 24 Mar 2026 22:54:25 -0700 [thread overview]
Message-ID: <acN4kVWoqbqbgi0t@infradead.org> (raw)
In-Reply-To: <51f57b049c46e9d22d69d2cb1589526814b9bf65@linux.dev>
On Wed, Mar 25, 2026 at 02:25:16AM +0000, sunliming@linux.dev wrote:
> > which could affect different test algorithms differently, so this is not
> > a good idea.
> >
> Yes，but this code can be compiled as a module，Could the same problem exist when loading the module?
It could. But at least it is under user control, while offloading
during normal boot almost guarantees a spiky load because that is
how the boot process works.
next prev parent reply other threads:[~2026-03-25 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 6:07 [PATCH RESEND v3 0/3] lib/raid6: Optimize raid6_select_algo to ensure sunliming
2026-03-20 6:07 ` [PATCH RESEND v3 1/3] lib/raid6: Divide the raid6 algorithm selection process into two parts sunliming
2026-03-24 7:55 ` Christoph Hellwig
2026-03-20 6:07 ` [PATCH RESEND v3 2/3] lib/raid6: Optimizing the raid6_select_algo time through asynchronous processing sunliming
2026-03-20 11:24 ` Paul Menzel
2026-03-24 7:56 ` Christoph Hellwig
[not found] ` <51f57b049c46e9d22d69d2cb1589526814b9bf65@linux.dev>
2026-03-25 5:54 ` Christoph Hellwig [this message]
2026-03-20 6:07 ` [PATCH RESEND v3 3/3] lib/raid6: Delete the RAID6_PQ_BENCHMARK config sunliming
-- strict thread matches above, loose matches on Subject: below --
2026-03-20 6:00 [PATCH RESEND v3 0/3] lib/raid6: Optimize raid6_select_algo to ensure sunliming
2026-03-20 6:00 ` [PATCH RESEND v3 2/3] lib/raid6: Optimizing the raid6_select_algo time through asynchronous processing sunliming
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=acN4kVWoqbqbgi0t@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=sunliming@kylinos.cn \
--cc=sunliming@linux.dev \
--cc=yukuai@fnnas.com \
/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