And of course numactl -H
will tell you which numa nodes are associated with which CPUs, at least down to the socket level. > On 2018, Jun 22, at 2:48 PM, Michael Di Domenico <mdidomeni...@gmail.com> > wrote: > > On Fri, Jun 22, 2018 at 2:44 PM, Skylar Thompson > <skylar.thomp...@gmail.com> wrote: >> On Friday, June 22, 2018, Michael Di Domenico <mdidomeni...@gmail.com> >> wrote: >>> >>> On Fri, Jun 22, 2018 at 2:28 PM, Skylar Thompson >>> <skylar.thomp...@gmail.com> wrote: >>>> Assuming Linux, you can get that information out of /proc/<pid>/smaps >>>> and >>>> numa_maps. >>> >>> the memory regions are in there for the used bits, but i don't have >>> anything that translates those regions to which cpu the region sits on >> >> I think the number before the = in the page count fields (Nn=pages) is the >> NUMA node number. Not exactly the CPU, but the memory isn't allocated to a >> specific CPU (modulo CPU cache). > > ah, spiffy. i glossed right over that in the manpage > _______________________________________________ > Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf _______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
