Date: Fri, 27 Apr 2012 16:37:41 -0700 From: Adrian Chadd <adrian@freebsd.org> To: David Christensen <davidch@broadcom.com> Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Andrey Zonov <andrey@zonov.org>, "davidch@freebsd.org" <davidch@freebsd.org> Subject: Re: bce: jumbo not working since r218423 Message-ID: <CAJ-VmokfS0r-aWOqOX6_CgUhuigyT9rLet8Tai2yA9qWEDpFhg@mail.gmail.com> In-Reply-To: <3A5015FE9E557D448AF7238AF0ACE20A129751@IRVEXCHMB11.corp.ad.broadcom.com> References: <CANU_PUGwoLSrPcGE8wT=ga3-=F_n9qN4pPXMJC%2BH72wpS9Mfcw@mail.gmail.com> <20120427230400.GB17009@michelle.cdnetworks.com> <3A5015FE9E557D448AF7238AF0ACE20A129751@IRVEXCHMB11.corp.ad.broadcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 April 2012 16:08, David Christensen <davidch@broadcom.com> wrote: > The intent was to pass compliance tests such as those performed at UNH > by limiting the MTU to the size allowed by the IEEE 802.3 specification. > (No one likes explaining such failures to customers.) =A0As you indicate,= real > world applications benefit from loose compliance on RX so a single > tunable is all that's intended to enable/disable the behavior. May I suggest (if it isn't already) documenting this in the driver manpage? that way it's not forgotten by some future hacker and removed for being "useless" ? :-) Thanks! Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokfS0r-aWOqOX6_CgUhuigyT9rLet8Tai2yA9qWEDpFhg>