On Fri, Nov 23, 2012 at 06:19:44PM +0000, Stuart Henderson wrote: > In some cases (especially 100Mb chips which support baby jumbos) > I know that they don't reflect the capability of the chip.
That wasn't the original intent when hardmtu was added, but it makes sense to allow for it. Although most if not all of the drivers will require some additional changes other than simply bumping up hardmtu. > For ethernet devices, except in the case of oce(4), if the driver > doesn't set hardmtu, the mtu can't be raised above ETHER_MTU. > (in most cases this is checked in ether_subr.c; oce and ix have > their own check in the driver). That is intentional. > It's possible to check driver source for this of course, but in > some cases like bge(4) it needs a bit of digging to work out > which chip family you have. IMO quite useful. One less thing to have to go digging through source to figure out. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
