Lines Matching full:flow
67 Software-generated layer two frames, like IEEE 802.3x (link flow control), IEEE
68 802.1Qbb (priority based flow-control), and others of this type, are not
190 Intel(R) Ethernet Flow Director
192 The Intel Ethernet Flow Director performs the following tasks:
195 - Enables tight control on routing a flow in the platform
196 - Matches flows and CPU cores for flow affinity
198 NOTE: This driver supports the following flow types:
209 Each flow type supports valid combinations of IP addresses (source or
216 L3 and L4 flow types are supported for user-defined flexible filters. For a
217 given flow type, you must clear all Intel Ethernet Flow Director filters before
218 changing the input set (for that flow type).
221 Flow Director Filters
223 Flow Director filters are used to direct traffic that matches specified
225 or disable the Intel Ethernet Flow Director and these filters::
239 # ethtool -U <ethX> flow-type <type> src-ip <ip> [m <ip_mask>] dst-ip <ip>
266 # ethtool -U <ethX> flow-type tcp4 src-ip 192.168.10.1 dst-ip \
271 # ethtool -U <ethX> flow-type tcp4 src-ip 192.168.10.1 dst-ip \
276 # ethtool -U <ethX> flow-type tcp4 src-ip 192.168.10.1 dst-ip \
285 # ethtool -U enp130s0 flow-type tcp4 src-ip 192.168.0.1 dst-ip 192.168.0.5
290 # ethtool -U <ethX> flow-type tcp4 src-ip 192.168.0.0 m 0.255.255.255 dst-ip
295 For each flow-type, the programmed filters must all have the same matching
298 # ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.1 src-port 5300 action 7
299 # ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.5 src-port 55 action 10
304 # ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.1 src-port 5300 action 7
305 # ethtool -U enp130s0 flow-type ip4 dst-ip 192.168.0.5 src-port 55 action 10
315 Flex Byte Flow Director Filters
340 flow-type tcp4 ... user-def 0x8BEAF ...
361 RSS Hash Flow
363 Allows you to set the hash bytes per flow type and any combination of one or
368 # ethtool -N <ethX> rx-flow-hash <type> <option>
395 Accelerated Receive Flow Steering (aRFS)
398 Accelerated Receive Flow Steering (aRFS) on the PF. aRFS is a load-balancing
400 application is running or consuming the packets in that flow.
411 - aRFS only supports Flow Director filters, which consist of the
413 - aRFS and ethtool's ntuple interface both use the device's Flow Director. aRFS
416 Flow Director" for additional information.
420 1. Enable the Intel Ethernet Flow Director and ntuple filters using ethtool.
426 2. Set up the number of entries in the global flow table. For example:
433 3. Set up the number of entries in the per-queue flow table. For example:
669 enabling flow control may mitigate the issue.
707 NOTE: The kernel assumes that TC0 is available, and will disable Priority Flow
714 priority flow control (802.1Qbb) which can limit or eliminate the number of
775 Flow Control
777 Ethernet Flow Control (IEEE 802.3x) can be configured with ethtool to enable
783 NOTE: You must have a flow control capable link partner.
785 Flow Control is disabled by default.
787 Use ethtool to change the flow control settings.
789 To enable or disable Rx or Tx Flow Control::
793 Note: This command only enables or disables Flow Control if auto-negotiation is
797 Note: Flow Control auto-negotiation is part of link auto-negotiation. Depending
802 - The ice driver requires flow control on both the port and link partner. If
803 flow control is disabled on one of the sides, the port may appear to hang on
805 - You may encounter issues with link-level flow control (LFC) after disabling