On Tue, Dec 13, 2016 at 01:15:11PM -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. You mean pmem that is DAX-capable that suddenly, without warning, becomes non-DAX capable? If you are not talking about pmem and DAX, then exactly what does "when a filesystem page is migrated to device memory that CPU can not access" mean? What "filesystem page" are we talking about that can get migrated from main RAM to something the CPU can't access? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
