From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: MengEn Sun <mengensun@tencent.com>,
Thomas Gleixner <tglx@linutronix.de>,
YueHong Wu <yuehongwu@tencent.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>
Subject: Re: [PATCH 0/4] ucount: Simplify refcounting with rcuref_t.
Date: Fri, 7 Feb 2025 21:48:54 +0100 [thread overview]
Message-ID: <20250207204854.rc1gron_@linutronix.de> (raw)
In-Reply-To: <20250203150525.456525-1-bigeasy@linutronix.de>
On 2025-02-03 16:05:21 [+0100], To linux-kernel@vger.kernel.org wrote:
> I noticed that the atomic_dec_and_lock_irqsave() in put_ucounts() loops
> sometimes even during boot. Something like 2-3 iterations but still.
> This series replaces the refcounting with rcuref_t and adds a RCU
> lookup.
> This allows a lockless lookup in alloc_ucounts() if the entry is
> available and a cmpxchg()less put of the item.
Andrew, could you please take this series?
Sebastian
prev parent reply other threads:[~2025-02-07 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:05 [PATCH 0/4] ucount: Simplify refcounting with rcuref_t Sebastian Andrzej Siewior
2025-02-03 15:05 ` [PATCH 1/4] rcu: Provide a static initializer for hlist_nulls_head Sebastian Andrzej Siewior
2025-02-03 15:05 ` [PATCH 2/4] ucount: Replace get_ucounts_or_wrap() with atomic_inc_not_zero() Sebastian Andrzej Siewior
2025-02-03 15:05 ` [PATCH 3/4] ucount: Use RCU for ucounts lookups Sebastian Andrzej Siewior
2025-02-03 15:05 ` [PATCH 4/4] ucount: Use rcuref_t for reference counting Sebastian Andrzej Siewior
2025-02-04 2:00 ` [PATCH 0/4] ucount: Simplify refcounting with rcuref_t Paul E. McKenney
2025-02-07 20:48 ` Sebastian Andrzej Siewior [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=20250207204854.rc1gron_@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mengensun@tencent.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=yuehongwu@tencent.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