From: Wei Chen <acee06.weichen@gmail.com>
To: linux-numa@vger.kernel.org
Subject: A question about numa_set_membind()
Date: Sun, 3 Jun 2012 12:45:07 +0900 [thread overview]
Message-ID: <CADbtAaKGc_N7xegjDixMiGJK85p0_Hm-O8yYvEA+4QkYQO0uDQ@mail.gmail.com> (raw)
Dear all,
Recently I am confused about numa_set_membind() for global arrays. If
we have a global array and later we call numa_set_membind() in our
code, will that global array be set to the node specified by the
nodemask_t. As I know, global array is allocated in the global data
area by the compiler before program executes. So I wonder whether
numa_set_membind() affects global variables and how. Besides, I would
like to know if there is one global data area for each node or all
memory only share one global data area. If all memory only share one
global data area, how to decide the distance between each node and the
global data area?
Thank you. I am looking forward to hearing from you.
Best regards,
Chen
next reply other threads:[~2012-06-03 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 3:45 Wei Chen [this message]
2012-06-03 18:31 ` A question about numa_set_membind() Andi Kleen
2012-06-04 1:45 ` Wei Chen
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=CADbtAaKGc_N7xegjDixMiGJK85p0_Hm-O8yYvEA+4QkYQO0uDQ@mail.gmail.com \
--to=acee06.weichen@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 read-only IMAP folder(s) and NNTP newsgroup(s).