1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Jumbo frames and windows mtu size

Discussion in 'Networking' started by Sylhouette, Oct 5, 2011.

  1. Sylhouette

    Sylhouette New Member

    Messages:
    185
    Likes Received:
    0
    Hello all.

    I am trying to use jumbo frames between my zfs iscsi target and my windows 2003 server

    Now i only have two mtu sizes on windows 4088 and 9014

    When i set my mtu size on my FreeBSD to the same, it feels like something is wrong.

    is windows mtu 9014 the same as 9000 on FreeBSD, if so what is the correct mtu size for 4088 then, it is not 4000, because if i set that, copies to the zfs iscsi target takes more time than the default 1500 value.


    regards
    Johan Hendriks
     
  2. yongari@

    yongari@ New Member Developer

    Messages:
    76
    Likes Received:
    0
    Have no experience on Windows server but I believe the meaning of MTU should be the same. Jumbo frame support highly depends on controller and driver quality. Even though both parties use different MTU value, TCP will use advertised MSS so there should be no problem in general.

    If you use non-server class controllers you'd better to stick on standard MTU. Server class controllers have better DMA engine and optimized for efficient packet processing for all frame size. Non-server class controllers have several limitations for certain frame size and generally they are tuned for standard MTU. I would choose best MTU value based on experimentation.

    For server class controllers, it's normal to see 990Mbps with jumbo frame for bulk TCP transfers. For non-server class controllers, the number would be 940-960Mbps with jumbo frame, so bottle-neck wouldn't be ethernet.
     
  3. Sylhouette

    Sylhouette New Member

    Messages:
    185
    Likes Received:
    0
    Thanks for your answer.

    The nics are two intel desktop cards.
    The performance with the default mtu size, is more than acceptable, so i leave it like it is.

    Thanks again.

    regards,
    Johan
     
  4. RusDyr

    RusDyr New Member

    Messages:
    83
    Likes Received:
    0
    "it feels like something is wrong" actually very unspecified problem. ;) I would recommend to check actual size in iSCSI traffic by tcpdump, turn on path mtu discovery temporary.
     
  5. Savagedlight

    Savagedlight Member

    Messages:
    360
    Likes Received:
    0
    Basically, the Windows setting includes the header bytes and the FreeBSD setting does not. If you set it to 9014 on Windows, your FreeBSD setting should be 9000. If you set it to 4088 on Windows, your FreeBSD setting should be (4088-14)=4074.