From: Andi Kleen <andi@firstfloor.org>
To: Rick Sherm <rick.sherm@yahoo.com>
Cc: linux-numa@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Memory policy question for NUMA arch....
Date: Wed, 7 Apr 2010 11:00:14 +0200 [thread overview]
Message-ID: <20100407090014.GD18855@one.firstfloor.org> (raw)
In-Reply-To: <524835.89860.qm@web114303.mail.gq1.yahoo.com>
On Tue, Apr 06, 2010 at 01:46:44PM -0700, Rick Sherm wrote:
> On a NUMA host, if a driver calls __get_free_pages() then
> it will eventually invoke ->alloc_pages_current(..). The comment
> above/within alloc_pages_current() says 'current->mempolicy' will be
> used.So what memory policy will kick-in if the driver is trying to
> allocate some memory blocks during driver load time(say from probe_one)? System-wide default policy,correct?
Actually the policy of the modprobe or the kernel boot up if built in
(which is interleaving)
>
> What if the driver wishes to i) stay confined to a 'cpulist' OR ii) use a different mem-policy? How
> do I achieve this?
> I will choose the 'cpulist' after I am successfuly able to affinitize the MSI-X vectors.
You can do that right now by running numactl ... modprobe ...
Yes there should be probably a better way, like using a policy
based on the affinity of the PCI device.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next parent reply other threads:[~2010-04-07 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524835.89860.qm@web114303.mail.gq1.yahoo.com>
2010-04-07 9:00 ` Andi Kleen [this message]
2010-04-07 15:48 ` Memory policy question for NUMA arch Rick Sherm
2010-04-07 17:27 ` Lee Schermerhorn
2010-04-20 20:34 Chetan Loke
[not found] <243351.5510.qm@web111910.mail.gq1.yahoo.com>
2010-04-16 23:17 ` Chetan Loke
2010-04-17 6:35 ` Andi Kleen
2010-04-17 14:59 ` Chetan Loke
2010-04-17 19:30 ` Andi Kleen
2010-04-19 15:16 ` Lee Schermerhorn
-- strict thread matches above, loose matches on Subject: below --
2010-04-06 19:29 Rick Sherm
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=20100407090014.GD18855@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-numa@vger.kernel.org \
--cc=rick.sherm@yahoo.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