lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 15 Sep 2010 10:57:34 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Joe Perches" <joe@...ches.com>
cc:	"Matthew Carlson" <mcarlson@...adcom.com>,
	"Benjamin Li" <benli@...adcom.com>,
	"David S. Miller" <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] drivers/net/tg3.c: Raise Jumbo Frame MTU to
 9216?


On Wed, 2010-09-15 at 10:41 -0700, Joe Perches wrote:
> The TG3 apparently supports 9K frame sizes.
> 
> http://www.broadcom.com/collateral/pb/5704C-PB05-R.pdf
> 
> Is exactly 9000 a hardware limit?
> 
> Should the jumbo frame MTU be raised to 9216 or 9216
> less the size of MAC, VLAN, IP and TCP headers?

9000 has been the de facto standard, has it been changed recently?

Anyway, we've never done any testing on 9216.  As it uses up to 2 more
internal mbufs per packet, there may not be sufficient buffers inside
the chip for optimal operations.  At best, some water marks will need to
be tweaked.  The hardware statistics counters (ethtool -S) also may not
work for packets bigger than 9022 bytes.

> 
> diff --git a/drivers/net/tg3.c b/drivers/net/tg3.c
> index 9f6ffff..3727070 100644
> --- a/drivers/net/tg3.c
> +++ b/drivers/net/tg3.c
> @@ -95,7 +95,7 @@
>  /* hardware minimum and maximum for a single frame's data payload */
>  #define TG3_MIN_MTU			60
>  #define TG3_MAX_MTU(tp)	\
> -	((tp->tg3_flags & TG3_FLAG_JUMBO_CAPABLE) ? 9000 : 1500)
> +	((tp->tg3_flags & TG3_FLAG_JUMBO_CAPABLE) ? 9216 : 1500)
>  
>  /* These numbers seem to be hard coded in the NIC firmware somehow.
>   * You can't change the ring sizes, but you can change where you place
> 
> 
> 


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ