From: Uladzislau Rezki <urezki@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, RCU <rcu@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Axtens <dja@axtens.net>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraju@codeaurora.org>,
Joel Fernandes <joel@joelfernandes.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Uladzislau Rezki <uladzislau.rezki@sony.com>
Subject: Re: [PATCH 1/1] rcu: Introduce CONFIG_RCU_EXP_CPU_STALL_TIMEOUT
Date: Thu, 17 Feb 2022 18:52:30 +0100 [thread overview]
Message-ID: <Yg6LXv+XS85TXoEb@pc638.lan> (raw)
In-Reply-To: <20220216195508.GM4285@paulmck-ThinkPad-P17-Gen-1>
On Wed, Feb 16, 2022 at 11:55:08AM -0800, Paul E. McKenney wrote:
> On Wed, Feb 16, 2022 at 02:52:09PM +0100, Uladzislau Rezki (Sony) wrote:
> > From: Uladzislau Rezki <uladzislau.rezki@sony.com>
> >
> > Currently for both expedited and regular grace periods stall
> > warnings are emitted based on one timeout value that is defined
> > in seconds. The problem is that, a stall timeout in seconds for
> > expedited grace period is a way long.
> >
> > The idea of expedited grace period is to force CPUs to report
> > their quiescent states as fast as possible. If in RCU read-side
> > critical section, it will request the next rcu_read_unlock() to
> > record the quiescent state. If not either it reports immediately
> > or set TIF_NEED_RESCHED to initiate the task switch.
> >
> > Therefore introduce the CONFIG_RCU_EXP_CPU_STALL_TIMEOUT kernel
> > configuration that is set to 20 msec. It also can be changed in
> > run-time via: /sys/.../parameters/rcu_exp_cpu_stall_timeout.
> >
> > Signed-off-by: Uladzislau Rezki <uladzislau.rezki@sony.com>
> > Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
>
> Nice, thank you!
>
> I have queued this, with the usual wordsmithing.
>
> I also changed the CONFIG_RCU_EXP_CPU_STALL_TIMEOUT kconfig option's
> default to be 20 milliseconds only no CONFIG_ANDROID=y kernel builds. For
> one, rcutorture gets expedited stall warnings even at 200 milliseconds,
> and for another, larger systems often have longer-running readers.
> It might be a very good thing to decrease the non-Android default
> expedited stall warning timeout, but 20 milliseconds is not likely the
> place to start that effort. Though it would be one way to find out
> when in the process large-system users started testing. ;-)
>
> My guess is that this change will result in some breakage even on Android,
> and that adjustments will be needed. Once that effort is complete,
> it would probably make sense to take another look at the non-Android
> default for CONFIG_RCU_EXP_CPU_STALL_TIMEOUT.
>
Yep, totally agree. There will be needed an addition adjustment later on to
find some better floor value :)
--
Vlad Rezki
prev parent reply other threads:[~2022-02-17 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 13:52 [PATCH 1/1] rcu: Introduce CONFIG_RCU_EXP_CPU_STALL_TIMEOUT Uladzislau Rezki (Sony)
2022-02-16 19:55 ` Paul E. McKenney
2022-02-17 17:52 ` Uladzislau Rezki [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=Yg6LXv+XS85TXoEb@pc638.lan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=dja@axtens.net \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=neeraju@codeaurora.org \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=uladzislau.rezki@sony.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