Messages in this thread | | | From | Ulrich Drepper <> | Date | Mon, 7 Apr 2014 21:56:41 -0400 | Subject | Re: 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.
| |