| 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: <alpine.DEB.2.02.1403312126580.20972@chino.kir.corp.google.com> Date: Mon, 31 Mar 2014 21:28:55 -0700 (PDT) From: David Rientjes <rientjes@...gle.com> To: Naoya Horiguchi <n-horiguchi@...jp.nec.com> cc: drepper@...il.com, anatol.pomozov@...il.com, jkosina@...e.cz, akpm@...ux-foundation.org, xemul@...allels.com, paul.gortmaker@...driver.com, linux-kernel@...r.kernel.org Subject: Re: NUMA node information for pages On Mon, 31 Mar 2014, Naoya Horiguchi wrote: > > I might be missing something but I couldn't find a way to use the > > pagemap information to then look up the NUMA node the respective page is > > located on. Especially when analyzing anomalities this is really > > useful. The /proc/kpageflags and /proc/kpagecount files don't have that > > information. > > > > If this is correct, could the attached patch be considered? It's really > > simple and follows the same line as the kpageflags file. > > The information about "pfn-node" mapping seldom (or never) changes after boot, > so it seems better to me that adding a new interface somewhere under > /sys/devices/system/node/nodeN which shows pfn range of a given node. If that's the direction we're going, I'd much prefer just the physical start and end addresses be exported rather than pfn so we don't need to do getpagesize() in userspace. -- 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