From: crocket <crockabiscuit@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: NFSv3 client caches dozens or hundreds of megabytes before sending a write request to NFS server.
Date: Sun, 17 Apr 2011 18:23:26 +0900 [thread overview]
Message-ID: <BANLkTi=3mcfWuFhoCzetzuguA2vA02AShg@mail.gmail.com> (raw)
Let me explain my network configuration.
Internet <--------------------> eth0 | the linux router | eth1
<------------------------------> eth0 | the desktop.
The linux router is actually a proper computer but not a router that
has linux firmware.
eth1 on the router and eth0 on the desktop are both full-duplex at 100Mbps.
The full-duplex connection is confirmed using netcat like
http://imagebin.org/148650
And they also remain full-duplex during NFS transfers according to "ethtool".
The router runs an NFS server, and the desktop uses an NFS client.
On the desktop, if I download files from the internet to the NFS
server, the client caches dozens or hundreds of megabytes before
sending data to the server like http://imagebin.org/148648
As a result, the download pauses frequently to send data to the NFS
server until the download is finished.
I want NFS client to forward downloaded data to the server immediately
instead of after caching.
In other words, I want NFS transfer to be http://imagebin.org/148650
but not http://imagebin.org/148648
Does anybody know how to solve this issue?
next reply other threads:[~2011-04-17 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 9:23 crocket [this message]
2011-04-17 13:21 ` NFSv3 client caches dozens or hundreds of megabytes before sending a write request to NFS server crocket
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='BANLkTi=3mcfWuFhoCzetzuguA2vA02AShg@mail.gmail.com' \
--to=crockabiscuit@gmail.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;
as well as URLs for NNTP newsgroup(s).