On Fri, Nov 23, 2012 at 06:19:44PM +, 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 mos
On Fri, Nov 23, 2012 at 5:16 PM, Reyk Floeter wrote:
> On Fri, Nov 23, 2012 at 04:04:20PM +, Stuart Henderson wrote:
>> This adds an ioctl to retrieve if_hardmtu, and adds code to
>> display it via ifconfig hwfeatures.
>>
>> $ ifconfig em0 hwfeatures
>> em0: flags=8b43 mtu
>> 1500
>> hw
On 2012/11/23 17:46, Christian Weisgerber wrote:
> Stuart Henderson wrote:
>
> > This adds an ioctl to retrieve if_hardmtu, and adds code to
> > display it via ifconfig hwfeatures.
>
> I'm worried that our drivers don't set this or that the value doesn't
> accurately reflect the capabilities of
On Fri, Nov 23, 2012 at 05:46:27PM +, Christian Weisgerber wrote:
> Stuart Henderson wrote:
>
> > This adds an ioctl to retrieve if_hardmtu, and adds code to
> > display it via ifconfig hwfeatures.
>
> I'm worried that our drivers don't set this or that the value doesn't
> accurately reflect
Stuart Henderson wrote:
> This adds an ioctl to retrieve if_hardmtu, and adds code to
> display it via ifconfig hwfeatures.
I'm worried that our drivers don't set this or that the value doesn't
accurately reflect the capabilities of chip/driver.
--
Christian "naddy" Weisgerber
On Fri, Nov 23, 2012 at 04:04:20PM +, Stuart Henderson wrote:
> This adds an ioctl to retrieve if_hardmtu, and adds code to
> display it via ifconfig hwfeatures.
>
> $ ifconfig em0 hwfeatures
> em0: flags=8b43 mtu
> 1500
> hwfeatures=30 hardmtu=16110
> lladdr f0:de:f1:f9:a7:52
>
This adds an ioctl to retrieve if_hardmtu, and adds code to
display it via ifconfig hwfeatures.
$ ifconfig em0 hwfeatures
em0: flags=8b43 mtu
1500
hwfeatures=30 hardmtu=16110
lladdr f0:de:f1:f9:a7:52
priority: 0
trunk: trunkdev trunk0
media: Ethernet autose
