From: Boqun Feng <boqun.feng@gmail.com>
To: linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Cc: Boqun Feng <boqun.feng@gmail.com>
Subject: [PATCH 0/6] RCU nocb updates for v6.9
Date: Wed, 31 Jan 2024 17:40:52 -0800 [thread overview]
Message-ID: <20240201014100.3204532-1-boqun.feng@gmail.com> (raw)
Hi,
This series contains the updates and fixes of RCU nocb for v6.9.
You can also find the series at:
https://github.com/fbq/linux.git rcu-nocb.2024.01.29a
The detailed list of the changes:
Frederic Weisbecker (4):
rcu/nocb: Remove needless LOAD-ACQUIRE
rcu/nocb: Remove needless full barrier after callback advancing
rcu/nocb: Make IRQs disablement symmetric
rcu/nocb: Re-arrange call_rcu() NOCB specific code
Zqiang (2):
rcu/nocb: Fix WARN_ON_ONCE() in the rcu_nocb_bypass_lock()
rcu/nocb: Check rdp_gp->nocb_timer in __call_rcu_nocb_wake()
kernel/rcu/tree.c | 53 +++++++++++++++++++++++-------------------
kernel/rcu/tree.h | 9 ++++---
kernel/rcu/tree_nocb.h | 47 ++++++++++++++++++++++---------------
3 files changed, 61 insertions(+), 48 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-01 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 1:40 Boqun Feng [this message]
2024-02-01 1:40 ` [PATCH 1/6] rcu/nocb: Remove needless LOAD-ACQUIRE Boqun Feng
2024-02-01 1:40 ` [PATCH 2/6] rcu/nocb: Remove needless full barrier after callback advancing Boqun Feng
2024-02-01 1:40 ` [PATCH 3/6] rcu/nocb: Make IRQs disablement symmetric Boqun Feng
2024-02-01 1:40 ` [PATCH 4/6] rcu/nocb: Re-arrange call_rcu() NOCB specific code Boqun Feng
2024-02-01 1:40 ` [PATCH 5/6] rcu/nocb: Fix WARN_ON_ONCE() in the rcu_nocb_bypass_lock() Boqun Feng
2024-02-24 16:30 ` Oleksandr Natalenko
2024-02-27 0:21 ` Paul E. McKenney
2024-02-01 1:40 ` [PATCH 6/6] rcu/nocb: Check rdp_gp->nocb_timer in __call_rcu_nocb_wake() Boqun Feng
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=20240201014100.3204532-1-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=linux-kernel@vger.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 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.