<br><br><div><span class="gmail_quote">On 12/29/05, <b class="gmail_sendername">Greg Oliver</b> <<a href="mailto:goliver@cistera.com">goliver@cistera.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jumbo frames are your friend<br><br>On Wed, 2005-12-28 at 21:29 -0800, Jonathan Tidmore wrote:<br>> On 12/28/05, Mike Frisch <<a href="mailto:mfrisch@isurfer.ca">mfrisch@isurfer.ca</a>> wrote:<br>><br>> The "tcp" option may not be necessary but I haven't taken the
<br>> time to<br>> benchmark between TCP and UDP.<br>><br>><br>> For gigabit ethernet, the nfs people recommend TCP.<br>><br>> From the man page for nfs (5):<br>><br>> WARNINGS<br>
> Using NFS over UDP on high-speed links such as Gigabit can<br>> cause silent data corruption.<br>><br>> The problem can be triggered
at high loads, and is caused<br>> by problems in IP fragment reassembly. NFS<br>> read and writes typically transmit UDP packets of 4 Kilobytes<br>> or more, which have to be broken up into<br>> several fragments in order to be
sent over the Ethernet<br>> link, which limits packets to 1500 bytes by<br>> default. This process happens at the IP network layer and is<br>> called fragmentation.<br>><br>> They go into greater detail about this issue. For info use 'man 5
<br>> nfs'<br>><br>><br>> -J<br>> _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a></blockquote><div><br>
<br>
Hmm, I wonder if this may be related to why nfs apparently locks my
machine in heavy use. It started when I switched to gigabit nics
and I was blaming the cards, until I realized I could do high data
transfers with the computer as long as I don't use nfs.<br>
</div><br>
Ryan<br></div><br>