On 12/16/2016 08:44 AM, Aneesh Kumar K.V wrote: > Jerome Glisse <jglisse@xxxxxxxxxx> writes: > >> 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. >> >> >> I also like to join discussions on: >> - Peer-to-Peer DMAs between PCIe devices >> - CDM coherent device memory >> - PMEM >> - overall mm discussions > I would like to attend this discussion. I can talk about coherent device > memory and how having HMM handle that will make it easy to have one > interface for device driver. For Coherent device case we definitely need > page cache migration support. I have been in the discussion on the mailing list about HMM since V13 which got posted back in October. Touched upon many points including how it changes ZONE_DEVICE to accommodate un-addressable device memory, migration capability of currently supported ZONE_DEVICE based persistent memory etc. Looked at the HMM more closely from the perspective whether it can also accommodate coherent device memory which has been already discussed by others on this thread. I too would like to attend to discuss more on this topic. -- 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
