From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: "Paul E . McKenney" <paulmck@kernel.org>
Cc: RCU <rcu@vger.kernel.org>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Boqun Feng <boqun.feng@gmail.com>,
Hillf Danton <hdanton@sina.com>,
Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: [PATCH v2 0/3] reduce latency of normal synchronize_rcu() v2
Date: Mon, 30 Oct 2023 14:12:51 +0100 [thread overview]
Message-ID: <20231030131254.488186-1-urezki@gmail.com> (raw)
v1 is here https://lore.kernel.org/lkml/20231025140915.590390-1-urezki@gmail.com/T/
The delta v1 -> v2:
- rework a commit message;
- use non-ordered __llist* API for a wait list manipulation.
The aim of this series is to reduce a latency, make synchronize_rcu()
more generic, unify it. Because currently a behavior depends much on
RCU kconfig combinations, like, CONFIG_RCU_NOCB_CPU, CONFIG_RCU_LAZY.
For example we have a soft-irq/ksoftirqd context or a regular kthread.
Uladzislau Rezki (Sony) (3):
rcu: Reduce synchronize_rcu() latency
rcu: Add a trace event for synchronize_rcu_normal()
doc: Add rcutree.rcu_normal_wake_from_gp to kernel-parameters.txt
.../admin-guide/kernel-parameters.txt | 14 ++
include/trace/events/rcu.h | 27 +++
kernel/rcu/tree.c | 156 +++++++++++++++++-
kernel/rcu/tree_exp.h | 2 +-
4 files changed, 197 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-10-30 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 13:12 Uladzislau Rezki (Sony) [this message]
2023-10-30 13:12 ` [PATCH v2 1/3] rcu: Reduce synchronize_rcu() latency Uladzislau Rezki (Sony)
2023-11-02 4:35 ` Paul E. McKenney
2023-11-06 12:04 ` Uladzislau Rezki
2023-11-07 5:32 ` Paul E. McKenney
2023-11-07 14:21 ` Uladzislau Rezki
2023-11-07 16:49 ` Paul E. McKenney
2023-11-08 10:56 ` Uladzislau Rezki
2023-11-08 15:24 ` Paul E. McKenney
2023-11-09 11:36 ` Z qiang
2023-11-09 12:34 ` Uladzislau Rezki
2023-10-30 13:12 ` [PATCH v2 2/3] rcu: Add a trace event for synchronize_rcu_normal() Uladzislau Rezki (Sony)
2023-11-02 4:36 ` Paul E. McKenney
2023-10-30 13:12 ` [PATCH v2 3/3] doc: Add rcutree.rcu_normal_wake_from_gp to kernel-parameters.txt Uladzislau Rezki (Sony)
2023-11-02 4:37 ` Paul E. McKenney
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=20231030131254.488186-1-urezki@gmail.com \
--to=urezki@gmail.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=hdanton@sina.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).