[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1105271157350.2533@chino.kir.corp.google.com>
Date: Fri, 27 May 2011 12:07:30 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Michal Hocko <mhocko@...e.cz>
cc: Andrew Morton <akpm@...ux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
LKML <linux-kernel@...r.kernel.org>,
Jack Steiner <steiner@....com>,
Lee Schermerhorn <lee.schermerhorn@...com>,
Christoph Lameter <cl@...ux-foundation.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Paul Menage <menage@...gle.com>, Robin Holt <holt@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org
Subject: Re: [PATCH v2] cpusets: randomize node rotor used in
cpuset_mem_spread_node()
On Fri, 27 May 2011, Michal Hocko wrote:
> > alpha allmodconfig:
> >
> > kernel/built-in.o: In function `cpuset_slab_spread_node':
> > (.text+0x67360): undefined reference to `node_random'
> > kernel/built-in.o: In function `cpuset_slab_spread_node':
> > (.text+0x67368): undefined reference to `node_random'
> > kernel/built-in.o: In function `cpuset_mem_spread_node':
> > (.text+0x673b8): undefined reference to `node_random'
> > kernel/built-in.o: In function `cpuset_mem_spread_node':
> > (.text+0x673c0): undefined reference to `node_random'
> >
> > because it has CONFIG_NUMA=n, CONFIG_NODES_SHIFT=7.
>
> non-NUMA with MAX_NUMA_NODES? Hmm, really weird and looks like a numa
> misuse.
>
CONFIG_NODES_SHIFT is used for UMA machines that are using DISCONTIGMEM
usually because they have very large holes; such machines don't need
things like mempolicies but do need the data structures that abstract
ranges of memory in the physical address space. This build breakage
probably isn't restricted to only alpha, you could probably see it with at
least ia64 and mips as well.
> Define node_random directly in the mempolicy header
>
> Alpha allows a strange configuration CONFIG_NUMA=n and CONFIG_NODES_SHIFT=7
> which means that mempolicy.c is not compiled and linked while we still have
> MAX_NUMNODES>1 which means that node_random is not defined.
>
It's not just alpha, and it's not entirely strange.
> Let's move node_random definition into the header. We will be consistent with
> other node_* functions.
>
> Signed-off-by: Michal Hocko <mhocko@...e.cz>
> Index: linus_tree/include/linux/nodemask.h
> ===================================================================
> --- linus_tree.orig/include/linux/nodemask.h 2011-05-27 14:15:52.000000000 +0200
> +++ linus_tree/include/linux/nodemask.h 2011-05-27 14:36:30.000000000 +0200
> @@ -433,7 +433,21 @@ static inline void node_set_offline(int
> nr_online_nodes = num_node_state(N_ONLINE);
> }
>
> -extern int node_random(const nodemask_t *maskp);
> +unsigned int get_random_int(void );
Spurious space.
> +/*
> + * Return the bit number of a random bit set in the nodemask.
> + * (returns -1 if nodemask is empty)
> + */
> +static inline int node_random(const nodemask_t *maskp)
> +{
> + int w, bit = -1;
> +
> + w = nodes_weight(*maskp);
> + if (w)
> + bit = bitmap_ord_to_pos(maskp->bits,
> + get_random_int() % w, MAX_NUMNODES);
> + return bit;
> +}
>
> #else
>
Probably should have a no-op definition when MAX_NUMNODES == 1 that just
returns 0?
> Index: linus_tree/mm/mempolicy.c
> ===================================================================
> --- linus_tree.orig/mm/mempolicy.c 2011-05-27 14:16:05.000000000 +0200
> +++ linus_tree/mm/mempolicy.c 2011-05-27 14:16:34.000000000 +0200
> @@ -1650,21 +1650,6 @@ static inline unsigned interleave_nid(st
> return interleave_nodes(pol);
> }
>
> -/*
> - * Return the bit number of a random bit set in the nodemask.
> - * (returns -1 if nodemask is empty)
> - */
> -int node_random(const nodemask_t *maskp)
> -{
> - int w, bit = -1;
> -
> - w = nodes_weight(*maskp);
> - if (w)
> - bit = bitmap_ord_to_pos(maskp->bits,
> - get_random_int() % w, MAX_NUMNODES);
> - return bit;
> -}
> -
> #ifdef CONFIG_HUGETLBFS
> /*
> * huge_zonelist(@vma, @addr, @gfp_flags, @mpol)
--
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