From: Ananya Muddukrishna <ananya@kth.se>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-numa@vger.kernel.org
Subject: Re: MPOL_INTERLEAVE page-wise binding dump
Date: Thu, 22 Dec 2011 21:52:03 +0100 [thread overview]
Message-ID: <20111222215203.5657d16f@aniX201> (raw)
In-Reply-To: <20111222195808.GE11715@one.firstfloor.org>
Hi,
> On Thu, 22 Dec 2011 20:58:08 +0100
> Andi Kleen <andi@firstfloor.org> wrote:
> On Thu, Dec 22, 2011 at 05:12:41PM +0000, Ananya Muddukrishna wrote:
> > Hi,
> >
> > Is there an inexpensive way to determine
> > which pages (virtual addresses)
> > are bound to which NUMA nodes when
> > using MPOL_INTERLEAVE or MPOL_BIND
> > with a given set of nodes?
>
>
> get_mempolicy MPOL_F_ADDR|MPOL_F_NODE
>
Thanks! I will check this out and get back. I hope this returns the
affinity as a page-to-node map.
> >
> > I want to implement a strict
> > round-robin based interleaving
> > policy based on MPOL_INTERLEAVE.
>
> What's the rationale?
The rationale relates to scheduling tasks (OpenMP and the like) with
page affinity in a user-level runtime system (work-crew threading
model).
The runtime system allocates memory pages in a deterministic way using
mbind and from then on, schedules tasks such that accesses to task
operated pages (affinity) do not incur large NUMA overheads. I am
thinking of using mlock so that swapin_readahead does not affect the
affinity of runtime-allocated pages. The first-touch policy is not of
much help since the allocated memory is initialized before tasks are
scheduled.
>
>
> -Andi
> --
> ak@linux.intel.com -- Speaking for myself only.
-- Ananya
next prev parent reply other threads:[~2011-12-22 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 17:12 MPOL_INTERLEAVE page-wise binding dump Ananya Muddukrishna
2011-12-22 19:58 ` Andi Kleen
2011-12-22 20:52 ` Ananya Muddukrishna [this message]
2011-12-22 20:56 ` Ananya Muddukrishna
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=20111222215203.5657d16f@aniX201 \
--to=ananya@kth.se \
--cc=andi@firstfloor.org \
--cc=linux-numa@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