On 04/22/2015 01:14 PM, Christoph Lameter wrote: > On Wed, 22 Apr 2015, Jerome Glisse wrote: > >> Glibc hooks will not work, this is about having same address space on >> CPU and GPU/accelerator while allowing backing memory to be regular >> system memory or device memory all this in a transparent manner to >> userspace program and library. > > If you control the address space used by malloc and provide your own > implementation then I do not see why this would not work.
Your program does not know how many other programs it is sharing the co-processor / GPU device with, which means it does not know how much of the co-processor or GPU memory will be available for it at any point in time. Well, in your specific case your program might know, but in the typical case it will not. This means the OS will have to manage the resource. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
