| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100407090014.GD18855@one.firstfloor.org> Date: Wed, 7 Apr 2010 11:00:14 +0200 From: Andi Kleen <andi@...stfloor.org> To: Rick Sherm <rick.sherm@...oo.com> Cc: linux-numa@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Memory policy question for NUMA arch.... 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@...ux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists