From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Dennis Zhou <dennis@kernel.org>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] percpu-refcount: Use normal instead of RCU-sched"
Date: Thu, 7 Nov 2019 17:28:42 +0100 [thread overview]
Message-ID: <20191107162842.2qgd3db2cjmmsxeh@linutronix.de> (raw)
In-Reply-To: <20191107161749.GA93945@dennisz-mbp>
On 2019-11-07 11:17:49 [-0500], Dennis Zhou wrote:
> Hello,
Hi,
> I just want to clarify a little bit. Is this patch aimed at fixing an
> issue with RT kernels specifically?
Due to the implications of preempt_disable() on RT kernels it fixes
problems with RT kernels.
> It'd also be nice to have the
> numbers as well as if the kernel was RT or non-RT.
The benchmark was done on a CONFIG_PREEMPT kernel. As said in the commit
log, the numbers were mostly the same, I can re-run the test and post
numbers if you want them.
This patch makes no difference on PREEMPT_NONE or PREEMPT_VOLUNTARY
kernels.
> Thanks,
> Dennis
Sebastian
next prev parent reply other threads:[~2019-11-07 16:28 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
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 [this message]
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=20191107162842.2qgd3db2cjmmsxeh@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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®