> We don't try to resolve "conflicting" writes between ordinary mmap() and > write(), so why should we be doing it for mmap and O_DIRECT? > > mmap() is designed to violate the ordinary mutex locks for write(), so > if a conflict arises, whether it be with O_DIRECT or ordinary writes > then it is a case of "last writer wins".
but.. wouldn't an O_DIRECT *read* even cause this? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
