From: Paul Mundt <lethal@linux-sh.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [v2,2/8] NUMA Hotplug emulator
Date: Mon, 15 Nov 2010 15:41:59 +0900 [thread overview]
Message-ID: <20101115064159.GF8489@linux-sh.org> (raw)
In-Reply-To: <20101113061445.GL32501@shaohui>
On Sat, Nov 13, 2010 at 02:14:45PM +0800, Shaohui Zheng wrote:
> diff --git a/include/linux/nodemask.h b/include/linux/nodemask.h
> index dba35e4..ba0f82d 100644
> --- a/include/linux/nodemask.h
> +++ b/include/linux/nodemask.h
> @@ -371,6 +371,10 @@ static inline void __nodes_fold(nodemask_t *dstp, const nodemask_t *origp,
> */
> enum node_states {
> N_POSSIBLE, /* The node could become online at some point */
> +#ifdef CONFIG_NODE_HOTPLUG_EMU
> + N_HIDDEN, /* The node is hidden at booting time, could be
> + * onlined in run time */
> +#endif
> N_ONLINE, /* The node is online */
> N_NORMAL_MEMORY, /* The node has regular memory */
> #ifdef CONFIG_HIGHMEM
> @@ -470,6 +474,13 @@ static inline int num_node_state(enum node_states state)
> #define node_online(node) node_state((node), N_ONLINE)
> #define node_possible(node) node_state((node), N_POSSIBLE)
>
> +#ifdef CONFIG_NODE_HOTPLUG_EMU
> +#define node_set_hidden(node) node_set_state((node), N_HIDDEN)
> +#define node_clear_hidden(node) node_clear_state((node), N_HIDDEN)
> +#define node_hidden(node) node_state((node), N_HIDDEN)
> +extern int hotadd_hidden_nodes(int nid);
> +#endif
> +
> #define for_each_node(node) for_each_node_state(node, N_POSSIBLE)
> #define for_each_online_node(node) for_each_node_state(node, N_ONLINE)
>
None of these really need to be under ifdef. Secondly, the description
you have provided is pretty ambiguous in comparison to N_POSSIBLE. Is
there some reason you can't just use N_POSSIBLE for this instead?
prev parent reply other threads:[~2010-11-15 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 6:14 [v2,2/8] NUMA Hotplug emulator Shaohui Zheng
2010-11-15 6:41 ` Paul Mundt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101115064159.GF8489@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox