Messages in this thread | | | From | Alan Cox <> | Subject | Re: [NFS] New version of Linux NFSv3 client is out... | Date | Tue, 25 Jan 2000 07:07:31 -0500 (EST) |
| |
> So what happens if I store a token in a store via NFS -- I write(2) > this token out, send a packet to something else which also has this > store mounted, is reads it and sees the _old_ data -- kaboom?
It is up to the client to avoid bypassed writes on its own write cache, inter client coherency isnt an NFS server issue. Basically NFS doesn't even try to get it right. Clients tend to use lockf as barrier points to commit. (ie flush before lockf, commit before unlock) but don't bet on it
Alan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |