From: "Paul E. McKenney" <paulmck@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Dennis Zhou <dennis@kernel.org>,
Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] percpu-refcount: Use normal instead of RCU-sched"
Date: Wed, 2 Oct 2019 08:08:52 -0700 [thread overview]
Message-ID: <20191002150852.GB2689@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20191002112252.ro7wpdylqlrsbamc@linutronix.de>
On Wed, Oct 02, 2019 at 01:22:53PM +0200, Sebastian Andrzej Siewior wrote:
> This is a revert of commit
> a4244454df129 ("percpu-refcount: use RCU-sched insted of normal RCU")
>
> which claims the only reason for using RCU-sched is
> "rcu_read_[un]lock() … are slightly more expensive than preempt_disable/enable()"
>
> and
> "As the RCU critical sections are extremely short, using sched-RCU
> shouldn't have any latency implications."
>
> The problem with using RCU-sched here is that it disables preemption and
> the callback must not acquire any sleeping locks like spinlock_t on
> PREEMPT_RT which is the case with some of the users.
Looks good in general, but changing to RCU-preempt does not change the
fact that the callbacks execute with bh disabled. There is a newish
queue_rcu_work() that invokes a workqueue handler after a grace period.
Or am I missing your point here?
Thanx, Paul
> Using rcu_read_lock() on PREEMPTION=n kernels is not any different
> compared to rcu_read_lock_sched(). On PREEMPTION=y kernels there are
> already performance issues due to additional preemption points.
> Looking at the code, the rcu_read_lock() is just an increment and unlock
> is almost just a decrement unless there is something special to do. Both
> are functions while disabling preemption is inlined.
> Doing a small benchmark, the minimal amount of time required was mostly
> the same. The average time required was higher due to the higher MAX
> value (which could be preemption). With DEBUG_PREEMPT=y it is
> rcu_read_lock_sched() that takes a little longer due to the additional
> debug code.
>
> Convert back to normal RCU.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>
> Benchmark https://breakpoint.cc/percpu_test.patch
>
> include/linux/percpu-refcount.h | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/include/linux/percpu-refcount.h b/include/linux/percpu-refcount.h
> index 7aef0abc194a2..390031e816dcd 100644
> --- a/include/linux/percpu-refcount.h
> +++ b/include/linux/percpu-refcount.h
> @@ -186,14 +186,14 @@ static inline void percpu_ref_get_many(struct percpu_ref *ref, unsigned long nr)
> {
> unsigned long __percpu *percpu_count;
>
> - rcu_read_lock_sched();
> + rcu_read_lock();
>
> if (__ref_is_percpu(ref, &percpu_count))
> this_cpu_add(*percpu_count, nr);
> else
> atomic_long_add(nr, &ref->count);
>
> - rcu_read_unlock_sched();
> + rcu_read_unlock();
> }
>
> /**
> @@ -223,7 +223,7 @@ static inline bool percpu_ref_tryget(struct percpu_ref *ref)
> unsigned long __percpu *percpu_count;
> bool ret;
>
> - rcu_read_lock_sched();
> + rcu_read_lock();
>
> if (__ref_is_percpu(ref, &percpu_count)) {
> this_cpu_inc(*percpu_count);
> @@ -232,7 +232,7 @@ static inline bool percpu_ref_tryget(struct percpu_ref *ref)
> ret = atomic_long_inc_not_zero(&ref->count);
> }
>
> - rcu_read_unlock_sched();
> + rcu_read_unlock();
>
> return ret;
> }
> @@ -257,7 +257,7 @@ static inline bool percpu_ref_tryget_live(struct percpu_ref *ref)
> unsigned long __percpu *percpu_count;
> bool ret = false;
>
> - rcu_read_lock_sched();
> + rcu_read_lock();
>
> if (__ref_is_percpu(ref, &percpu_count)) {
> this_cpu_inc(*percpu_count);
> @@ -266,7 +266,7 @@ static inline bool percpu_ref_tryget_live(struct percpu_ref *ref)
> ret = atomic_long_inc_not_zero(&ref->count);
> }
>
> - rcu_read_unlock_sched();
> + rcu_read_unlock();
>
> return ret;
> }
> @@ -285,14 +285,14 @@ static inline void percpu_ref_put_many(struct percpu_ref *ref, unsigned long nr)
> {
> unsigned long __percpu *percpu_count;
>
> - rcu_read_lock_sched();
> + rcu_read_lock();
>
> if (__ref_is_percpu(ref, &percpu_count))
> this_cpu_sub(*percpu_count, nr);
> else if (unlikely(atomic_long_sub_and_test(nr, &ref->count)))
> ref->release(ref);
>
> - rcu_read_unlock_sched();
> + rcu_read_unlock();
> }
>
> /**
> --
> 2.23.0
>
next prev parent reply other threads:[~2019-10-02 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 11:22 Sebastian Andrzej Siewior
2019-10-02 15:08 ` Paul E. McKenney [this message]
2019-10-02 15:17 ` Sebastian Andrzej Siewior
2019-11-07 9:13 ` Sebastian Andrzej Siewior
2019-11-07 16:17 ` Dennis Zhou
2019-11-07 16:28 ` Sebastian Andrzej Siewior
2019-11-07 16:55 ` Dennis Zhou
2019-11-07 17:24 ` Sebastian Andrzej Siewior
2019-11-07 17:36 ` Dennis Zhou
2019-11-08 17:35 ` [PATCH v2] " Sebastian Andrzej Siewior
2019-11-08 18:17 ` Christopher Lameter
2019-11-11 10:44 ` Sebastian Andrzej Siewior
2019-11-11 13:38 ` Paul E. McKenney
2019-11-17 4:11 ` Dennis Zhou
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=20191002150852.GB2689@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@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
all inboxes | Powered by JetHome®