From: Nick Piggin <piggin@cyberone.com.au>
To: Martin Hicks <mort@wildopensource.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __alloc_pages - NUMA and lower zone protection
Date: Sat, 14 Feb 2004 11:01:08 +1100 [thread overview]
Message-ID: <402D6544.2080300@cyberone.com.au> (raw)
In-Reply-To: <20040213183243.GH12142@localhost>
Martin Hicks wrote:
>Hi,
>
>There is a problem with the current __alloc pages on a machine with many
>nodes. As we go down the zones[] list, we may move onto other nodes.
>Each time we go to the next zone we protect these zones by doing
>"min += local_low".
>
>This is quite appropriate on a machine with one node, but wrong on
>machines with other nodes. To illustrate, here is an example. On a
>256 node Altix machine, a request on node 0 for 2MB requires just over
>600MB of free memory on the 256th node in order to fullfil the "min"
>requirements if all other nodes are low on memory. This could leave
>73GB of memory unallocated across all nodes.
>
>This patch keeps the same semantics for lower_zone_protection, but only
>provides protection for higher priority zones in the same node.
>
>The patch seems to do the right thing on my non-NUMA zx1 ia64 machine
>(which has ZONE_DMA and ZONE_NORMAL) as well as the multi-node Altix.
>
>
Could you add a comment or two, please?
next prev parent reply other threads:[~2004-02-14 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 18:32 [PATCH] __alloc_pages - NUMA and lower zone protection Martin Hicks
2004-02-14 0:01 ` Nick Piggin [this message]
2004-02-14 2:17 ` Martin Hicks
2004-02-17 22:58 ` Andrew Morton
2004-02-18 16:19 ` Martin Hicks
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=402D6544.2080300@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@wildopensource.com \
/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.