It seems "noac" mount option enables direct write to the NFS server. Now the NFS client doesn't cache but write directly to the server. Please refer to "man nfs" if you use linux. On Sun, Apr 17, 2011 at 6:23 PM, crocket <crockabiscuit@xxxxxxxxx> wrote: > 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? > -- 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
