Yes. MS_ASYNC is "advisory" only, as I understand it. (too bad it isn't
select()'able actually, I could use that to work wonders with a database
engine here...)
>
> > Like any local-disk backed file.
> >
> > Ignoring the case where the NFS *server* crashes, where could the write
> > ordering differ, compared to local disk files ?
>
> > In other words, what does Benjamin's "unexpected ways" refer to ?
>
> All local clients will see the mmap() being updated from the time it is
> dirtied, but there is no ordering of write()s with respect to the mmap
> unless you explicitely msync(..MS_SYNC..) as in your example.
Ok, so we're talking multiple processes reading/writing.
Now it makes a lot more sense - I was thinking one process only. Silly
simple-minded me ;)
Thanks,
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob Østergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/