From: Daniel J Blueman <daniel@numascale.com>
To: Filipe Brandenburger <filbranden@google.com>,
Cliff Wickman <cpw@sgi.com>,
linux-numa@vger.kernel.org
Cc: Steffen Persvold <sp@numascale.com>
Subject: numaplace tool
Date: Tue, 24 Feb 2015 11:31:17 +0800 [thread overview]
Message-ID: <54EBF085.8000902@numascale.com> (raw)
Cliff, Filipe et al,
I've been developing a tool called numaplace [1,2] which gives run-time
task affinity; this is needed when booting with the 'isolcpus' kernel
parameter.
Secondly, it dynamically allocates (and locks out) cores at
task-creation time, giving a kind of run-time resource scheduling; this
allows users to execute OpenMP/threaded/multi-process applications
without preparing environment variables with explicit list of cores.
Later, I'll add NUMA locality guidance for improved spatial locality.
The numactl package seems a natural place to contribute this to, yes?
Many thanks!
Daniel
--
[1] https://wiki.numascale.com/tips/numaplace
[2] https://github.com/numascale/nc-utils/tree/master/os/numaplace
--
Daniel J Blueman
Principal Software Engineer, Numascale
reply other threads:[~2015-02-24 3:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54EBF085.8000902@numascale.com \
--to=daniel@numascale.com \
--cc=cpw@sgi.com \
--cc=filbranden@google.com \
--cc=linux-numa@vger.kernel.org \
--cc=sp@numascale.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).