On Wed, 22 Apr 2015, Benjamin Herrenschmidt wrote: > Right, it doesn't look at all like what we want. Its definitely a way to map memory that is outside of the kernel managed pool into a user space process. For that matter any device driver could be doing this as well. The point is that we already have pletora of features to do this. Putting new requirements on the already warped-and-screwed-up-beyond-all-hope zombie of a page allocator that we have today is not the way to do this. In particular what I have head repeatedly is that we do not want kernel structures alllocated there but then we still want to use this because we want malloc support in libraries. The memory has different performance characteristics (for starters there may be lots of other isssues depending on the device) so we just add a NUMA "node" with estremely high distance. There are hooks in glibc where you can replace the memory management of the apps if you want that. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>