Hello, hwloc 1.0 was released in May. I think we should release 1.1 before SC10, which means doing a first RC within a couple weeks.
trunk got many changes since 1.0, but nothing very important. trac says we're missing memory binding, distances and user-defined process restrictions. Memory binding is the most important one, it was supposed to be in 1.0. I think we shouldn't defer 1.1 because of the others. There are still some problems to solve in the membind branch: * Some OS bind the process too when you bind memory. I see the following solutions: + Add a flag such as HWLOC_MEMBIND_EVEN_IF_FAR_FROM_PROCESS so that the user can explicitly refuse memory binding if it may break process binding + Drop hwloc_set_membind on these OSes and add a hwloc_set_cpumembind() to bind both + Make both process and memory binding do nothing if the STRICT flag is given. But I'd rather not play too much with this flag. + Drop support for memory binding on these OS. + Drop these OS. * cpuset and nodeset structures are the same, they are both manipulated with hwloc_cpuset_foo functions. So maybe rename into hwloc_set_t and hwloc_set_foo functions. With #define and aliases to not break API/ABIs. Opinions ? Brice
