On 2018-12-04 1:14 p.m., Andi Kleen wrote: >> Also, in the same vein, I think it's wrong to have the API enumerate all >> the different memory available in the system. The API should simply > We need an enumeration API too, just to display to the user what they > have, and possibly for applications to size their buffers > (all we do with existing NUMA nodes) Yes, but I think my main concern is the conflation of the enumeration API and the binding API. An application doesn't want to walk through all the possible memory and types in the system just to get some memory that will work with a couple initiators (which it somehow has to map to actual resources, like fds). We also don't want userspace to police itself on which memory works with which initiator. Enumeration is definitely not the common use case. And if we create a new enumeration API now, it may make it difficult or impossible to unify these types of memory with the existing NUMA node hierarchies if/when this gets more integrated with the mm core. Logan
