Lines Matching refs:be

22     be changed (enabled or disabled) for a particular device by user's
23     request.  This set should be initialized in ndo_init callback and not
27     for a device.  This should be changed only by network core or in
38     networking core and should not be referenced in drivers.
45 When current feature set (netdev->features) is to be changed, new set
62 netdev_update_features() while holding rtnl_lock. This should not be done
63 from ndo_*_features callbacks. netdev->features should not be modified by
73 All dependencies between features should be resolved here. The resulting
74 set can be reduced further by networking core imposed limitations (as coded
78 This callback should not modify hardware nor driver state (should be
79 stateless).  It can be called multiple times between successive
84 care must be taken as the change won't affect already configured VLANs.
88 Hardware should be reconfigured to match passed feature set. The set
89 should not be altered unless some error condition happens that can't
90 be reliably detected in ndo_fix_features. In this case, the callback
92 Errors returned are not (and cannot be) propagated anywhere except dmesg.
109 whatever headers there might be.
114 set, be it TCPv4 (when NETIF_F_TSO is enabled) or TCPv6 (NETIF_F_TSO6).
134 NETIF_F_LLTX should be set in drivers that implement their own locking in
151 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN
153 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
154 VLANs. This may be not useful, though.]
165 frames (such as bad FCS, etc).  This can be helpful when sniffing a link with