Hi, We have direct I/O(O_DIRECT), for example raw devices(/dev/rawctl) that map to the block devices and we also have page cache. Now If I've understood this correctly, direct I/O will bypass this page cache, which is fine, I'll not get into the performance debate, but what about data consistency. Kernel cannot and __should'nt__ try to control how the applications are being written. So one bad day somebody comes up with an application which does both these two types of IO(one that goes through page cache and the other that doesn't) and in that application, one instance is writing directly to the backend device and the other instance, who is not aware of this write, goes ahead and writes to the page cache, and that write would be written later to the backend device. So wouldn't we end up corrupting the on disk data. I can think of multiple other scenarios which could corrupt the on-disk data, if there isn't any safeguarding policies employed by the kernel. But I'm very much sure that kernel is aware of such nasty attempts, and I'd like to know how does kernel takes care of this. !!amit _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
