From: Venkatesh K S <vsharma@sonoasystems.com>
To: nfs@lists.sourceforge.net
Subject: FILE_SYNC slower than UNSTABLE + COMMIT
Date: 13 Jan 2007 09:56:14 +0530 [thread overview]
Message-ID: <jeirfb4knt.fsf@sonoasystems.com> (raw)
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
next reply other threads:[~2007-01-13 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 4:26 Venkatesh K S [this message]
2007-01-13 21:43 ` FILE_SYNC slower than UNSTABLE + COMMIT Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeirfb4knt.fsf@sonoasystems.com \
--to=vsharma@sonoasystems.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox