Hello That's not how current operating systems work, hence hwloc cannot do it. Usually you can bind a process virtual memory to a specific part of the physical memory (a NUMA node is basically a big static range), but the reverse isn't allowed by any OS I know.
If you can tweak the hardware, you could try tweaking the ACPI tables so that a specific range of physical memory moves a new dedicated NUMA node :) Another crazy idea is to tell the Linux kernel at boot that your ranges aren't RAM but non-volatile memory. They won't be used by anybody by default, but you can make them "dax" devices that programs could mmap. Brice Le 21/12/2018 à 21:11, Dahai Guo a écrit : > Hi, > > I was wondering if there is a good way in hwloc to bind a particular > range of memory to a process? For example, suppose there are totally > 1000MB on the node, how to bind memory range [50, 100] to a process, > and [101,200] to another one? > > If hwloc can, an example will be greatly appreciated. > > D. > > _______________________________________________ > hwloc-users mailing list > email@example.com > https://lists.open-mpi.org/mailman/listinfo/hwloc-users
_______________________________________________ hwloc-users mailing list firstname.lastname@example.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users