lkml.org 
[lkml]   [2014]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: NUMA node information for pages
On Mon, Mar 31, 2014 at 9:24 PM, Naoya Horiguchi
<n-horiguchi@ah.jp.nec.com> wrote:
> 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 this doesn't work for your usecase, could you explain more about how you
> use this information?

I have no problem with that type of interface. It'll be more work
figuring out the details since the interface I proposed is trivial and
mimics that of kpageflags etc but that's manageable.

I'll see whether I can figure out the necessary details. I imagine
that if the PFN are indeed always clustered for each node then, as
David proposes, text output like

PFNSTART PFNSTOP

in a file below /sys/devices/system/node/nodeN should be sufficient.

How does memory hot plug work in this situation? If the PFNs are
allocated dense at startup then there might potentially be many ranges
for each node.


\
 
 \ /
  Last update: 2014-04-08 04:41    [W:0.095 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site