[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YULyLRwSJ6jj1bTF@hirez.programming.kicks-ass.net>
Date: Thu, 16 Sep 2021 09:28:45 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, mingo@...nel.org, jiangshanlai@...il.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, rostedt@...dmis.org,
dhowells@...hat.com, edumazet@...gle.com, fweisbec@...il.com,
oleg@...hat.com, joel@...lfernandes.org
Subject: Re: [PATCH rcu 10/14] rcu: Make rcutree_dying_cpu() use its "cpu"
parameter
On Wed, Sep 15, 2021 at 04:33:39PM -0700, Paul E. McKenney wrote:
> The CPU-hotplug functions take a "cpu" parameter, but rcutree_dying_cpu()
> ignores it in favor of this_cpu_ptr(). This works at the moment, but
> it would be better to be consistent. This might also work better given
> some possible future changes. This commit therefore uses per_cpu_ptr()
> to avoid ignoring the rcutree_dying_cpu() function's argument.
>
> Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
I think even in the old days dying and starting ran on the affected CPU,
and I don't ever see that changing.
Then again, none of this is hot-path in any way, so *meh* :-)
Powered by blists - more mailing lists