Messages in this thread |  | | From | Daniel Phillips <> | Subject | Re: invalidate_inode_pages in 2.5.32/3 | Date | Thu, 12 Sep 2002 21:06:20 +0200 |
| |
On Tuesday 10 September 2002 21:04, Chuck Lever wrote: > when locking or unlocking a file, the idea is to make sure that other > clients can see all changes to the file that were made while it was > locked. locking and unlocking provide tighter cache coherency than simple > everyday close-to-open because that's why applications go to the trouble > of locking a file -- they expect to share the contents of the file with > other applications on other clients. > > when a file is locked, the client wants to be certain it has the latest > version of the file for an application to play with. the cache is purged > to cause the client to read any recent changes from the server. when a > file is unlocked, the client wants to share its changes with other clients > so it flushes all pending writes before allowing the unlocking application > to proceed.
This is clear and easy to understand, thanks.
-- Daniel - 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/
|  |