[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200714205326.GY9247@paulmck-ThinkPad-P72>
Date: Tue, 14 Jul 2020 13:53:26 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
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 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.
> 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.
Are you good with giving Ulad a few days to produce his patch?
We do have at least a week or two before the merge window opens,
after all.
Thanx, Paul
Powered by blists - more mailing lists