public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
	lee.schermerhorn@hp.com, bob.picco@hp.com, clameter@sgi.com
Subject: Re: + numa-generic-management-of-nodemasks-for-various-purposes.patch added to -mm tree
Date: Sun, 29 Jul 2007 04:59:51 -0700	[thread overview]
Message-ID: <20070729045951.55b2285b.pj@sgi.com> (raw)
In-Reply-To: <200707290715.l6T7FtN8013215@imap1.linux-foundation.org>

Lee Schermerhorn (via Andrew) wrote:
> +static inline void node_set_state(int node, enum node_states state)
> +{
> +	__node_set(node, &node_states[state]);
> +}
> +
> +static inline void node_clear_state(int node, enum node_states state)
> +{
> +	__node_clear(node, &node_states[state]);
> +}


Lee - would you get the same result (same compiled binary code) with
something like:

+static inline void node_set_state(int node, enum node_states state)
+{
+	node_set(node, node_states[state]);
+}
+
+static inline void node_clear_state(int node, enum node_states state)
+{
+	node_clear(node, node_states[state]);
+}

If so, then I're prefer the latter, as it doesn't depend on the strange
#define wrapping an inline implementation of node_set and node_clear.

In other words, the latter looks 'simpler'.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

       reply	other threads:[~2007-07-29 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200707290715.l6T7FtN8013215@imap1.linux-foundation.org>
2007-07-29 11:59 ` Paul Jackson [this message]
2007-07-30 21:43   ` + numa-generic-management-of-nodemasks-for-various-purposes.patch added to -mm tree Lee Schermerhorn
2007-07-30 22:00     ` Christoph Lameter

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=20070729045951.55b2285b.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=bob.picco@hp.com \
    --cc=clameter@sgi.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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