[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: src/sys/dev/pci
(2013/07/04 1:35), Erik Fair wrote:
> It would be very helpful to document in bge(4) just which chips support jumbo
> frames (and how big).
I agree with you..... and I knew bge.4 is very obsolete..... :-(
> Heck, it would be even more helpful if that was a capability that ifconfig(8)
> could report because drivers declare it.
Yes, I think ifconfig should report the hard limit of MTU, too.
OpenBSD has SIOCGIFHARDMTU and ifconfig print the limit using with the ioctl.
It could be implemented using proplib, but I think ioctl is better than proplib
to be consistent with SIOC[GS]MTU.
> Erik <fair%netbsd.org@localhost>
> On Jul 2, 2013, at 22:49 , SAITOH Masanobu <msaitoh%netbsd.org@localhost>
>> Module Name: src
>> Committed By: msaitoh
>> Date: Wed Jul 3 05:49:36 UTC 2013
>> Modified Files:
>> src/sys/dev/pci: if_bge.c
>> Log Message:
>> Add BGE_JUMBO_CAPABLE flag to some chips. Before this commit,
>> the following chips support the jumbo frame function:
>> With this commit, the following chip support it, too:
>> 5719 (exclude rev. A0)
>> To generate a diff of this commit:
>> cvs rdiff -u -r1.253 -r1.254 src/sys/dev/pci/if_bge.c
>> Please note that diffs are not public domain; they are subject to the
>> copyright notices on the relevant files.
SAITOH Masanobu (msaitoh%execsw.org@localhost
* 英語 - 自動検出
Main Index |
Thread Index |