On Wed, 2010-02-03 at 17:44 -0600, Ben Myers wrote: > In April I did some research on why synchronous NFSv3 performance on XFS is so > rotten when compared to local filesystem performance. The workload I chose to > work with is tar. > > After taking some measurements I came to the conclusion that one of the big > problems is that we're not treating the log as stable storage. By calling > write_inode_now() we've written the changes to the log first and then gone and > also written them out to the inode on disk. > > In a short discussion of this issue on the xfs-oss list it was suggested that I > post the patches here for discussion. > > The following series is adds a 'wsync' export option to nfsd. It is intended > to be used on XFS with the wsync mount option. When you already have a > synchronous log there is no need to sync metadata separately. Why should the administrator have to both change /etc/fstab and /etc/exports? That will be an immediate source of trouble if someone changes one without changing the other. Why not rather add an optional operation to the export_ops to let the filesystem specify exactly what kind of synchronisation policy is optimal for it? Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
