Messages in this thread | | | Date | Mon, 7 Jun 2004 12:13:04 -0400 | From | Joe Korty <> | Subject | Re: [BUG] NFS no longer updates file modification times appropriately |
| |
On Mon, Jun 07, 2004 at 11:51:49AM -0400, Trond Myklebust wrote: > P? m? , 07/06/2004 klokka 11:21, skreiv Joe Korty: > > Unless the real reason is reducing ethernet traffic. > > That is after all, why we cache data. Look at the GETATTR traffic using > nfsstat. > > > In which case we > > could defer a timestamp-on-write only when it is still in the same second > > as the previous write, but don't defer when a new second rolls around > > on the client. That would reduce timestamp updates to at most one per > > second per inode per client, while preserving old NFS behavior. > > Exactly why should we go to all this trouble?
For compatibility? - 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/
| |