Lines Matching +full:hw +full:- +full:gro

1 .. SPDX-License-Identifier: GPL-2.0
8 	Michał Mirosław <mirq-[email protected]>
24  1. netdev->hw_features set contains features whose state may possibly
29  2. netdev->features set contains features which are currently enabled
33  3. netdev->vlan_features set contains features whose state is inherited
34     by child VLAN devices (limits netdev->features set).  This is currently
38  4. netdev->wanted_features set contains feature set requested by user.
40     some device-specific conditions change. This set is internal to
48 When current feature set (netdev->features) is to be changed, new set
52 returns success) replaces value stored in netdev->features.
66 from ndo_*_features callbacks. netdev->features should not be modified by
94 should update netdev->features to match resulting hardware state.
111 It means that device can fill TCP/UDP-like checksum anywhere in the packets
131  * Transmit scatter-gather
134 NETIF_F_SG --- paged skbs (skb_shinfo()->frags), NETIF_F_FRAGLIST ---
135 chained skbs (skb->next/prev list).
146 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
149 *  rx-fcs
155 *  rx-all
162 *  rx-gro-hw
164 This requests that the NIC enables Hardware GRO (generic receive offload).
165 Hardware GRO is basically the exact reverse of TSO, and is generally
166 stricter than Hardware LRO.  A packet stream merged by Hardware GRO must
167 be re-segmentable by GSO or TSO back to the exact original packet stream.
168 Hardware GRO is dependent on RXCSUM since every packet successfully merged
171 * hsr-tag-ins-offload
173 This should be set for devices which insert an HSR (High-availability Seamless
176 * hsr-tag-rm-offload
178 This should be set for devices which remove HSR (High-availability Seamless
181 * hsr-fwd-offload
183 This should be set for devices which forward HSR (High-availability Seamless
186 * hsr-dup-offload
188 This should be set for devices which duplicate outgoing HSR (High-availability