On Tue, 2016-12-13 at 13:15 -0500, Jerome Glisse wrote: > I would like to discuss un-addressable device memory in the context > of filesystem and block device. Specificaly how to handle write-back, > read, ... when a filesystem page is migrated to device memory that > CPU can not access. > > I intend to post a patchset leveraging the same idea as the existing > block bounce helper (block/bounce.c) to handle this. I believe this > is worth discussing during summit see how people feels about such > plan and if they have better ideas. Isn't this pretty much what the transcendent memory interfaces we currently have are for? It's current use cases seem to be compressed swap and distributed memory, but there doesn't seem to be any reason in principle why you can't use the interface as well. James > I also like to join discussions on: > - Peer-to-Peer DMAs between PCIe devices > - CDM coherent device memory > - PMEM > - overall mm discussions > > Cheers, > Jérôme > -- > To unsubscribe from this list: send the line "unsubscribe linux > -fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- 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>