Re: [hwloc-users] unusual memory binding results

2019-01-25 Thread Biddiscombe, John A.
> move_pages() returning 0 with -14 in the status array? As opposed to > move_pages() returning -1 with errno set to 14, which would definitely be a > bug in hwloc. I think it was move_pages returning zero with -14 in the status array, and then hwloc returning 0 with an empty nodeset (which I

Re: [hwloc-users] unusual memory binding results

2019-01-25 Thread Brice Goglin
Le 25/01/2019 à 14:17, Biddiscombe, John A. a écrit : > Dear List/Brice > > I experimented with disabling the memory touch on threads except for > N=1,2,3,4 etc and found a problem in hwloc, which is that the function > hwloc_get_area_memlocation was returning '0' when the status of the memory

Re: [hwloc-users] unusual memory binding results

2019-01-25 Thread Biddiscombe, John A.
Dear List/Brice I experimented with disabling the memory touch on threads except for N=1,2,3,4 etc and found a problem in hwloc, which is that the function hwloc_get_area_memlocation was returning '0' when the status of the memory null move operation was -14 (#define EFAULT 14 /* Bad address