All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix build_zonelists for CONFIG_ACPI_NUMA
Date: Thu, 18 Sep 2003 19:59:08 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106391520008530@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106383460616067@msgid-missing>

On Thu, Sep 18, 2003 at 08:38:32AM -0700, Jesse Barnes wrote:
> On Thu, Sep 18, 2003 at 05:16:33PM +0200, Erich Focht wrote:
> > The first node in the list is fine and we'll get memory from the right
> > node if it is free. But if not, we'll request memory from the second
> > node in the zonelist and this will be (in most of the cases) node
> > 1. Which means a pretty bad imbalance.
> 
> Yeah, that's a good point.  We should fix that.

On second thought, here's the output from a test machine here.  I think
it's working correctly.

...
ACPI 2.0 SLIT locality table:
010 020 022 042
020 010 042 022
022 042 010 020
042 022 020 010
...
Zonelist for node 0: 0 1 2 3
Zonelist for node 1: 1 0 3 2
Zonelist for node 2: 2 3 0 1
Zonelist for node 3: 3 2 1 0
...

So the fallback for nodes 0 and 1 (which are in the same proximity
domain) rotates the distant proximity domain correctly.  Same for nodes
2 and 3.

As opposed to:
...
Zonelist for node 0: 0 1 2 3
Zonelist for node 1: 1 0 2 3
Zonelist for node 2: 2 3 0 1
Zonelist for node 3: 3 2 0 1
...

Which I think you were worried about?

Thanks,
Jesse

  parent reply	other threads:[~2003-09-18 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 21:31 [PATCH] fix build_zonelists for CONFIG_ACPI_NUMA Jesse Barnes
2003-09-18 15:16 ` Erich Focht
2003-09-18 15:38 ` Jesse Barnes
2003-09-18 16:49 ` Erich Focht
2003-09-18 19:59 ` Jesse Barnes [this message]
2003-09-18 20:04 ` Jesse Barnes
2003-09-19 16:56 ` Erich Focht
2003-09-19 17:07 ` Jesse Barnes
2003-09-19 17:49 ` Paul Jackson

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=marc-linux-ia64-106391520008530@msgid-missing \
    --to=jbarnes@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.