[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200714190253.ylqjif7frqs2rq7x@linutronix.de>
Date: Tue, 14 Jul 2020 21:02:53 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: mingo@...nel.org, linux-kernel@...r.kernel.org,
rcu@...r.kernel.org, arnd@...db.de, elver@...gle.com, ethp@...com,
frederic@...nel.org, jbi.octave@...il.com, joel@...lfernandes.org,
lihaoliang@...gle.com, madhuparnabhowmik10@...il.com,
mchehab+huawei@...nel.org, peter.enderborg@...y.com,
rdunlap@...radead.org, richard.weiyang@...ux.alibaba.com,
urezki@...il.com, zou_wei@...wei.com, tglx@...utronix.de
Subject: Re: [GIT PULL tip/core/rcu] RCU commits for v5.9
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.
I also had a patch in my series to keep the lock/unlock path symmetrical
and it I think that I the only one that is missing it.
> Thanx, Paul
Sebastian
Powered by blists - more mailing lists