From: Venkatesh K S <vsharma@sonoasystems.com>
Subject: FILE_SYNC slower than UNSTABLE + COMMIT
Date: 13 Jan 2007 09:56:14 +0530
Message-ID: <jeirfb4knt.fsf@sonoasystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

Hi,

I have 2 different kernel versions and I notice that the way
the nfs client honors O_SYNC is different.
In 2.6.12 variant the client issues UNSTABLE followed by
a COMMIT call.
In 2.6.16 variant the nfs client issues a FILE_SYNC call.

The FILE_SYNC call turns out to be about 3 times slower
against our server. Infact a simple write followed by a
fsync also turns out to be FILE_SYNC calls. The mount
is not a "sync" mount.


Is there a way a to make these calls in 2.6.16 or later release
UNSTABLE + COMMIT ?

Are FILE_SYNC calls always slower (I wud assume for NVRAM based server
it may be as fast as UNSTABLE). In which case this fix into a newer
kernel seems to be biased towards working well with such servers

regards,
-venkatesh


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs