On Fri, 2015-04-24 at 22:32 -0400, Rik van Riel wrote: > > The result would be that the kernel would allocate only > migratable > > pages within the CCAD device's memory, and even then only if > > memory was otherwise exhausted. > > Does it make sense to allocate the device's page tables in memory > belonging to the device? > > Is this a necessary thing with some devices? Jerome's HMM comes > to mind...
In our case, the device's MMU shares the host page tables (which is why we can't use HMM, ie we can't have a page with different permissions on CPU vs. device which HMM does). However the device has a pretty fast path to system memory, the best thing we can do is pin the workload to the same chip the device is connected to so those page tables arent' too far away. Cheers, Ben. -- 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/
