From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@kernel.org>
Subject: [Question] : tie a task to a cluster when it shares memory resources
Date: Tue, 29 Oct 2013 10:32:33 -0700 [thread overview]
Message-ID: <526FF131.3070105@linaro.org> (raw)
Hi all,
I am not expert on the NUMA area and the scheduler but I was wondering
the following:
On numa a process can define a memory policy to optimize access because
remote memory access is suboptimal.
On a multicluster (aka multipackage), eg. Bi-Xeon 4 cores, the scheduler
load balancing can spawn/balance a task to the second cluster even if
the task is resulting from a fork or a pthread_create. If I am correct
that could impact the performances due to L2 cache misses, no ?
Won't it be more efficient to tie a task to a cluster when it shares
memory resources with another task on the same cluster ? and when the
task does 'exec', this constraint is removed.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
reply other threads:[~2013-10-29 17:32 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=526FF131.3070105@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 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.