From: Uladzislau Rezki <urezki@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
mingo@kernel.org, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, arnd@arndb.de, elver@google.com,
ethp@qq.com, frederic@kernel.org, jbi.octave@gmail.com,
joel@joelfernandes.org, lihaoliang@google.com,
madhuparnabhowmik10@gmail.com, mchehab+huawei@kernel.org,
peter.enderborg@sony.com, rdunlap@infradead.org,
richard.weiyang@linux.alibaba.com, urezki@gmail.com,
zou_wei@huawei.com, tglx@linutronix.de
Subject: Re: [GIT PULL tip/core/rcu] RCU commits for v5.9
Date: Tue, 14 Jul 2020 22:06:16 +0200 [thread overview]
Message-ID: <20200714200616.GA20137@pc636> (raw)
In-Reply-To: <20200714190253.ylqjif7frqs2rq7x@linutronix.de>
On Tue, Jul 14, 2020 at 09:02:53PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-07-14 11:27:32 [-0700], Paul E. McKenney wrote:
> > I believe that Ulad and Joel are working on an update.
>
> I expressed multiple times that I am unhappy with the raw_spinlock_t
> which both want to keep. It is important to be future proof but at the
> same time I am not sure if they know how many in-hardirq kmalloc() or
> kfree() invocation we have as of today in PREEMPT_RT.
>
It is not about counting how many times kfree_rcu() gets called from
the hard IRQ context for RT kernel. In fact it is about breaking of
such possibility if a conversion to spinlock_t is done. Is not it?
As a result the revert would change a behavior of the API function,
that is used to accept such usage. That is a motivation.
--
Vlad Rezki
next prev parent reply other threads:[~2020-07-14 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 17:27 [GIT PULL tip/core/rcu] RCU commits for v5.9 Paul E. McKenney
2020-07-14 18:14 ` Sebastian Andrzej Siewior
2020-07-14 18:27 ` Paul E. McKenney
2020-07-14 19:02 ` Sebastian Andrzej Siewior
2020-07-14 20:06 ` Uladzislau Rezki [this message]
2020-07-14 20:53 ` Paul E. McKenney
2020-07-15 7:15 ` Sebastian Andrzej Siewior
2020-07-14 20:17 ` Uladzislau Rezki
2020-07-15 14:12 ` Paul E. McKenney
2020-07-30 22:20 ` Ingo Molnar
2020-07-30 23:15 ` 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=20200714200616.GA20137@pc636 \
--to=urezki@gmail.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=elver@google.com \
--cc=ethp@qq.com \
--cc=frederic@kernel.org \
--cc=jbi.octave@gmail.com \
--cc=joel@joelfernandes.org \
--cc=lihaoliang@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peter.enderborg@sony.com \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=richard.weiyang@linux.alibaba.com \
--cc=tglx@linutronix.de \
--cc=zou_wei@huawei.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 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.