[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131016083813.GQ10651@twins.programming.kicks-ass.net>
Date: Wed, 16 Oct 2013 10:38:13 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Christoph Lameter <cl@...ux.com>
Cc: Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
rostedt@...dmis.org, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Alex Shi <alex.shi@...el.com>
Subject: Re: [PATCH 3/6] mm: Use raw_cpu ops for determining current NUMA node
On Tue, Oct 15, 2013 at 12:47:25PM -0500, Christoph Lameter wrote:
> Index: linux/include/linux/topology.h
> ===================================================================
> --- linux.orig/include/linux/topology.h 2013-09-24 11:29:51.000000000 -0500
> +++ linux/include/linux/topology.h 2013-09-24 11:30:18.893831971 -0500
> @@ -182,7 +182,7 @@ DECLARE_PER_CPU(int, numa_node);
> /* Returns the number of the current Node. */
> static inline int numa_node_id(void)
> {
> - return __this_cpu_read(numa_node);
> + return raw_cpu_read(numa_node);
> }
> #endif
>
> @@ -239,7 +239,7 @@ static inline void set_numa_mem(int node
> /* Returns the number of the nearest Node with memory */
> static inline int numa_mem_id(void)
> {
> - return __this_cpu_read(_numa_mem_);
> + return raw_cpu_read(_numa_mem_);
> }
> #endif
NAK; smp_processor_id() has the preemption checks; for consistently
numa_node_id() should have them too, for the very same reason. Who's to
say the node id is still valid when you return from this function? If
we're preemptable we could've just been migrated away to another node.
So please introduce raw_numa_node_id() and use that; all fully analogous
to smp_processor_id().
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists