A network interface driver can support IFCAP_VLAN_MTU only,
without IFCAP_VLAN_HWTAGGING. The previous version of the leading comment in this file could lead to the opposite conclusion. Fix some typos in the comment as well.
This commit is contained in:
parent
ed4788962e
commit
a4e16ddd8d
@ -62,10 +62,10 @@ struct vlanreq {
|
||||
/*
|
||||
* Drivers that are capable of adding and removing the VLAN header
|
||||
* in hardware indicate they support this by marking IFCAP_VLAN_HWTAGGING
|
||||
* in if_capabilities. Drivers for hardware that is also capable
|
||||
* in if_capabilities. Drivers for hardware that is capable
|
||||
* of handling larger MTU's that may include a software-appended
|
||||
* VLAN header w/o lowering the normal MTU should mark IFCAP_VLA_MTU
|
||||
* in if_capabilities; this notfies the VLAN code it can leave the
|
||||
* VLAN header w/o lowering the normal MTU should mark IFCAP_VLAN_MTU
|
||||
* in if_capabilities; this notifies the VLAN code it can leave the
|
||||
* MTU on the vlan interface at the normal setting.
|
||||
*/
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user