> In the case of read cache (which is probably going to be used more
> often than write-cache), the client needs to send two RPC every time
> a writer modifies the cached file. What if Rlease doesn't necessary
> break the lease, but have an option (negotiated in Tcache) to let the
> client know that the file is changed without breaking the lease.
>
> Thanks,
> Lucho
Another point in this discussion:
1. Most files are not shared
2. Some files are read-shared
3. Very, very few files are read-write shared
(Satya did some research on this at CMU — quite some time ago)
Having said that, we do want correct semantics all the time,
especially for read-write sharing.
A file server can use heuristics to decide the time out for leases.
For example, it could always grant 10-minute leases to begin with.
Doesn't cost a thing unless the client refuses to return a lease early
(but clients will be rarely asked to do so).
With updates in the recent past, or with the first occurrence of
read-write sharing, lease times can be drastically reduced.
Note that for files not shared or read-shared, call backs do not happen,
so lease calls will occur at the rate of the lease time, which is
once every few minutes. Big deal.
Sape
