From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Yajun Deng <yajun.deng@linux.dev>
Cc: song@kernel.org, masahiroy@kernel.org, williams@redhat.com,
pmenzel@molgen.mpg.de, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org, linux-raid@vger.kernel.org,
stable@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH v3] lib/raid6: Reduce high latency by using migrate instead of preempt
Date: Fri, 17 Dec 2021 14:42:17 +0100 [thread overview]
Message-ID: <YbyTuRWkB0gYbn7x@linutronix.de> (raw)
In-Reply-To: <20211217021610.12801-1-yajun.deng@linux.dev>
On 2021-12-17 10:16:10 [+0800], Yajun Deng wrote:
> We found an abnormally high latency when executing modprobe raid6_pq, the
> latency is greater than 1.2s when CONFIG_PREEMPT_VOLUNTARY=y, greater than
> 67ms when CONFIG_PREEMPT=y, and greater than 16ms when CONFIG_PREEMPT_RT=y.
>
> How to reproduce:
> - Install cyclictest
> sudo apt install rt-tests
> - Run cyclictest example in one terminal
> sudo cyclictest -S -p 95 -d 0 -i 1000 -D 24h -m
> - Modprobe raid6_pq in another terminal
> sudo modprobe raid6_pq
>
> This is caused by ksoftirqd fail to scheduled due to disable preemption,
> this time is too long and unreasonable.
>
> Reduce high latency by using migrate_disabl()/emigrate_enable() instead of
> preempt_disable()/preempt_enable(), the latency won't greater than 100us.
>
> This patch beneficial for CONFIG_PREEMPT=y or CONFIG_PREEMPT_RT=y, but no
> effect for CONFIG_PREEMPT_VOLUNTARY=y.
Why does it matter? This is only during boot-up/ module loading or do I
miss something?
The delay is a jiffy so it depends on CONFIG_HZ. You do benchmark for
the best algorithm and if you get preempted during that period then your
results may be wrong and you make a bad selection.
You can either enable one algorithm and or disable
CONFIG_RAID6_PQ_BENCHMARK. I don't see the need for this patch not to
mention the stable tree.
Sebastian
next prev parent reply other threads:[~2021-12-17 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 2:16 [PATCH v3] lib/raid6: Reduce high latency by using migrate instead of preempt Yajun Deng
2021-12-17 13:42 ` Sebastian Andrzej Siewior [this message]
2021-12-17 17:25 ` Song Liu
2021-12-17 18:17 ` Sebastian Andrzej Siewior
2021-12-17 22:01 ` Daniel Vacek
2021-12-17 21:58 ` Daniel Vacek
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=YbyTuRWkB0gYbn7x@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
--cc=yajun.deng@linux.dev \
/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