From: Olga Kornievskaia <aglo@citi.umich.edu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org
Subject: size of nfsv4 writes
Date: Wed, 04 Jun 2008 12:40:38 -0400 [thread overview]
Message-ID: <4846C586.1050000@citi.umich.edu> (raw)
While testing NFSv4 performance over the 10GE network, we are seeing the
following behavior and would like to know if it is normal or a bug in
the client code.
The server offers the max_write of 1M. The client mounts the server with
the "wsize" option of 1M. Yet during the write we are seeing that the
write size is at most 49K. Why does client never come close to 1M limit?
Thanks.
-Olga
next reply other threads:[~2008-06-04 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 16:40 Olga Kornievskaia [this message]
2008-06-04 16:46 ` size of nfsv4 writes Trond Myklebust
2008-06-04 22:04 ` Olga Kornievskaia
2008-06-06 0:25 ` Dean Hildebrand
2008-06-12 21:41 ` Olga Kornievskaia
2008-06-13 16:33 ` Chuck Lever
2008-06-13 18:19 ` Olga Kornievskaia
2008-06-13 19:03 ` 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=4846C586.1050000@citi.umich.edu \
--to=aglo@citi.umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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