public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] Re: fix zonelist ordering for NUMA
Date: Fri, 27 Feb 2004 00:56:45 +0000	[thread overview]
Message-ID: <124100000.1077843405@flay> (raw)
In-Reply-To: <100070000.1077834062@flay>

--On Thursday, February 26, 2004 16:47:10 -0800 Chris Wedgwood <cw@f00f.org> wrote:

> On Thu, Feb 26, 2004 at 02:21:02PM -0800, Martin J. Bligh wrote:
> 
>> +#ifndef node_distance
>> +#define node_distance(from,to) (1)
>> +#endif
> 
> 1 or 0 here?

Dunno ... was from j-nomura@ce.jp.nec.com, but I'd guess 1 makes more
sense semantically - we're saying the distance between nodes on a flat
NUMA architecture is equal (I think ;-))

M.


  parent reply	other threads:[~2004-02-27  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 22:21 [Lse-tech] Re: fix zonelist ordering for NUMA Martin J. Bligh
2004-02-26 23:09 ` Matthew Dobson
2004-02-26 23:40 ` Dave Hansen
2004-02-26 23:54 ` Martin J. Bligh
2004-02-27  0:47 ` Chris Wedgwood
2004-02-27  0:56 ` Martin J. Bligh [this message]
2004-02-27  5:38 ` j-nomura

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=124100000.1077843405@flay \
    --to=mbligh@aracnet.com \
    --cc=linux-ia64@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