From: Petr Holasek <pholasek@redhat.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: Jon Stanley <jonstanley@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
linux-numa@vger.kernel.org
Subject: Re: numactl using it's own affinity to determine CPU set
Date: Tue, 23 Oct 2012 23:17:08 +0200 [thread overview]
Message-ID: <20121023211707.GA6827@stainedmachine.redhat.com> (raw)
In-Reply-To: <20121023141918.GA27082@sgi.com>
On Tue, 23 Oct 2012, Cliff Wickman wrote:
> Hi Petr,
>
> On Tue, Oct 23, 2012 at 02:21:40PM +0200, Petr Holasek wrote:
> > btw, Cliff, can you remember what was the reason for this change in some
> > version after 1.0?
> >
> > Petr
>
> Memory nodes allowed was made cpuset-aware by the below patch.
> I'm not quite sure if this is the change you are asking about.
>
> patch 0804_ls_patch2
> From: Lee Schermerhorn <lee.schermerhorn@hp.com>
> Date: Wed, 02 Apr 2008 14:34:37 -0400
>
> Depends-on: MPOL_F_MEMS_ALLOWED kernel patch
> Provide libnuma API for MPOL_F_MEMS_ALLOWED flag.
> Return nodes allowed by the application's current cpuset context
> via new API numa_get_mems_allowed().
>
> +.BR numa_get_mems_allowed()
> +returns the mask of nodes from which the process is allowed to allocate
> +memory in it's current cpuset context.
Thank you!
I'll check it.
Petr
prev parent reply other threads:[~2012-10-23 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 19:35 numactl using it's own affinity to determine CPU set Jon Stanley
2012-10-22 19:41 ` Andi Kleen
2012-10-22 20:12 ` Jon Stanley
2012-10-23 12:21 ` Petr Holasek
2012-10-23 14:19 ` Cliff Wickman
2012-10-23 21:17 ` Petr Holasek [this message]
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=20121023211707.GA6827@stainedmachine.redhat.com \
--to=pholasek@redhat.com \
--cc=andi@firstfloor.org \
--cc=cpw@sgi.com \
--cc=jonstanley@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).