RE: calculate correct MTU size for jumbo frames?

  • From: "Matthew Zito" <mzito@xxxxxxxxxxx>
  • To: "Matthew Zito" <mzito@xxxxxxxxxxx>, <martin.a.berger@xxxxxxxxx>, "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Sun, 9 Nov 2008 00:56:21 -0500

It's too late here, I neglected to include the URL -

Also, another way to tell is to use a tool like tcpdump/wireshark and watch the 
cache fusion traffic and see if the frames are being fragmented.

Finally, this also doesn't apply if you're using something like LACP or 802.1q, 
both of which will increase the frame overhead due to additional metadata.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Matthew Zito
Sent: Sun 11/9/2008 12:21 AM
To: martin.a.berger@xxxxxxxxx; ORACLE-L
Subject: RE: calculate correct MTU size for jumbo frames?

9000 is the most commonly used value, and as a nice round value, less 
opportunity for misconfiguration.  Some old switches could only do 4400 bytes, 
but at this point, you should just set it at 9k with the rest of the world ;)

If you did want to calculate, you just need to sort out ethernet overhead + ip 
overhead + tcp overhead, which based on this site (first hit on ethernet 
overhead on google) is 44 bytes.


Other related posts: