From: Christoph Lameter <christoph@lameter.com>
To: Paul Jackson <pj@sgi.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] String conversions for memory policy
Date: Sat, 30 Jul 2005 10:56:55 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0507301042420.26355@graphe.net> (raw)
In-Reply-To: <20050729230026.1aa27e14.pj@sgi.com>
On Fri, 29 Jul 2005, Paul Jackson wrote:
> Oh - I should have mentioned this before - if you are displaying and
> parsing node lists (nodemask_t) then there are wrappers for these
> bitmap routines in linux/nodemask.h:
>
> * int nodemask_scnprintf(buf, len, mask) Format nodemask for printing
> * int nodemask_parse(ubuf, ulen, mask) Parse ascii string as nodemask
> * int nodelist_scnprintf(buf, len, mask) Format nodemask as list for printing
> * int nodelist_parse(buf, map) Parse ascii string as nodelist
>
> See nodemask.h for other such useful routines.
Hmmm. Would be great if we had a nodelist in the policy structure but it
is a zonelist instead and my conversion functions deal with zonelists and
not nodelists. Strangely mpol_new converts a node bit mask into a
list of zones.
As a consequence the zonelist always begins with zones of the lowest node.
Page allocation will therefore always fill up the lower nodes before going
to the higher nodes. Is this what we intended? I would have expected that
BIND would restrict to a set of nodes and then allocate locally on the
node the process is running on if possible. That is at least what I
gather from reading the documentation.
Maybe I do not fully understand what is going on here but this kind of
implementation for bind must be hurting performance of applications by
not allocating pages locally. It also puts extremely high
memory pressure on lower numbered nodes.
next prev parent reply other threads:[~2005-07-30 17:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 18:38 Christoph Lameter
2005-07-29 22:20 ` Paul Jackson
2005-07-30 0:53 ` Christoph Lameter
2005-07-30 5:54 ` Paul Jackson
2005-07-30 15:48 ` Christoph Lameter
2005-07-31 1:45 ` Paul Jackson
2005-07-30 6:00 ` Paul Jackson
2005-07-30 17:56 ` Christoph Lameter [this message]
2005-07-31 1:14 ` Paul Jackson
2005-07-31 1:21 ` Christoph Lameter
2005-07-31 1:50 ` Paul Jackson
2005-07-31 2:01 ` Paul Jackson
2005-07-31 2:05 ` Christoph Lameter
2005-07-31 2:12 ` Paul Jackson
2005-07-31 2:15 ` Christoph Lameter
2005-08-01 18:48 ` Christoph Lameter
2005-08-01 18:54 ` Christoph Lameter
2005-08-01 23:03 ` Paul Jackson
2005-08-01 23:24 ` Christoph Lameter
2005-08-01 23:59 ` Paul Jackson
2005-08-02 0:03 ` Christoph Lameter
2005-08-02 0:15 ` Christoph Lameter
2005-08-02 5:33 ` Paul Jackson
2005-08-02 6:11 ` Christoph Lameter
2005-08-03 5:44 ` Paul Jackson
2005-08-03 16:19 ` Christoph Lameter
2005-08-02 17:49 ` Christoph Lameter
2005-08-03 5:42 ` Paul Jackson
2005-08-03 8:48 ` Andi Kleen
2005-08-04 14:11 ` Christoph Lameter
2005-08-04 14:29 ` Andi Kleen
2005-08-04 16:31 ` Christoph Lameter
2005-08-04 17:08 ` Andi Kleen
2005-08-04 17:34 ` NUMA policy interface Christoph Lameter
2005-08-04 21:14 ` Andi Kleen
2005-08-04 21:21 ` Christoph Lameter
2005-08-04 21:41 ` Andi Kleen
2005-08-04 22:19 ` Christoph Lameter
2005-08-04 22:44 ` Mike Kravetz
2005-08-04 23:40 ` Andi Kleen
2005-08-04 23:49 ` Christoph Lameter
2005-08-05 9:16 ` Andi Kleen
2005-08-05 14:52 ` Christoph Lameter
2005-08-05 14:58 ` 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=Pine.LNX.4.62.0507301042420.26355@graphe.net \
--to=christoph@lameter.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®