On 26.06.2014 13:57, Luká? Czerner wrote: > > So if the authors want to sell this new interface (in whatever form) to > > the kernel community, they should start with providing a solid use-case, > > with some more details, explore alternatives and show how the > > alternatives do not work for them. > > Yes please, let's see some solid use-case for this. Personally i would want it to verify files after copying them: Especially while moving files: - Copy a file - <drop cache> - Verify that it really is correct on stable storage - Remove original file Currently i choose either of the 3 ways: - drop_caches - umount/mount - Write more data than memory in machine (Which is only an approximnation and you have to verify in the same order the files were written, so it is likely that any cache was thrashed in the meantime) But having a way to selectivly "destory" the cache of a file would make this task easier. -- Matthias -- 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
