Lines Matching +full:per +full:- +full:port
1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Intel(R) Ethernet Flow Director
16 - Additional Configurations
17 - Known Issues
18 - Support
47 ----------------------
49 …intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-m…
64 -----------------------
76 ------------------------
77 Allows you to send all packets with a specific VLAN tag to a particular SR-IOV
100 NOTE: By default, the ethtool priv-flag vf-true-promisc-support is set to
105 #ethtool -set-priv-flags p261p1 vf-true-promisc-support on
107 The vf-true-promisc-support priv-flag does not enable promiscuous mode; rather,
111 vf-true-promisc-support priv-flag is only exposed to the first PF of the
113 regardless of the vf-true-promisc-support setting.
124 -------------------------------
127 - Directs receive packets according to their flows to different queues.
128 - Enables tight control on routing a flow in the platform.
129 - Matches flows and CPU cores for flow affinity.
130 - Supports multiple parameters for flexible flow classification and load
137 destination port, or any combination of one or more of these four parameters.
140 user-defined flexible two-byte pattern and offset by using the ethtool user-def
141 and mask fields. Only L3 and L4 flow types are supported for user-defined
147 # ethtool -K ethX ntuple <on|off>
150 the driver cache and hardware. All needed filters must be re-added when ntuple
151 is re-enabled.
153 To add a filter that directs packet to queue 2, use -U or -N switch::
155 # ethtool -N ethX flow-type tcp4 src-ip 192.168.10.1 dst-ip \
156 192.168.10.2 src-port 2000 dst-port 2001 action 2 [loc 1]
160 # ethtool -N ethX flow-type tcp4 src-ip 192.168.10.1 dst-ip \
165 # ethtool <-u|-n> ethX
168 --------------------------------------------------
170 An ATR Intel Ethernet Flow Director filter rule is added when a TCP-IP flow
171 starts and is deleted when the flow ends. When a TCP-IP Intel Ethernet Flow
173 driver. To re-enable ATR, the sideband can be disabled with the ethtool -K
176 ethtool -K [adapter] ntuple [off|on]
178 If sideband is re-enabled after ATR is re-enabled, ATR remains enabled until a
179 TCP-IP flow is added. When all TCP-IP sideband rules are deleted, ATR is
180 automatically re-enabled.
186 ------------------------
191 ethtool -U <device> flow-type <type> src-ip <ip> dst-ip <ip> src-port <port> \
192 dst-port <port> action <queue>
195 <device> - the ethernet device to program
196 <type> - can be ip4, tcp4, udp4, or sctp4
197 <ip> - the ip address to match on
198 <port> - the port number to match on
199 <queue> - the queue to direct traffic towards (-1 discards matching traffic)
203 ethtool -u <device>
207 ethtool -U <device> delete <N>
212 The following example matches TCP traffic sent from 192.168.0.1, port 5300,
213 directed to 192.168.0.5, port 80, and sends it to queue 7::
215 ethtool -U enp130s0 flow-type tcp4 src-ip 192.168.0.1 dst-ip 192.168.0.5 \
216 src-port 5300 dst-port 80 action 7
218 For each flow-type, the programmed filters must all have the same matching
221 ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.1 src-port 5300 action 7
222 ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.5 src-port 55 action 10
225 specifies src-ip and the second specifies dst-ip::
227 ethtool -U enp130s0 flow-type ip4 src-ip 192.168.0.1 src-port 5300 action 7
228 ethtool -U enp130s0 flow-type ip4 dst-ip 192.168.0.5 src-port 55 action 10
234 Matching on a sub-portion of a field is not supported by the i40e driver, thus
237 The driver also supports matching user-defined data within the packet payload.
238 This flexible data is specified using the "user-def" field of the ethtool
241 +----------------------------+--------------------------+
243 +----------------------------+--------------------------+
245 +----------------------------+--------------------------+
251 ... user-def 0x4FFFF ...
259 flow-type tcp4 ... user-def 0x8BEAF ...
273 The user-defined flexible offset is also considered part of the input set and
292 Setting the link-down-on-close Private Flag
293 -------------------------------------------
294 When the link-down-on-close private flag is set to "on", the port's link will
297 Use ethtool to view and set link-down-on-close, as follows::
299 ethtool --show-priv-flags ethX
300 ethtool --set-priv-flags ethX link-down-on-close [on|off]
302 Setting the mdd-auto-reset-vf Private Flag
303 ------------------------------------------
305 When the mdd-auto-reset-vf private flag is set to "on", the problematic VF will
309 Use ethtool to view and set mdd-auto-reset-vf, as follows::
311 ethtool --show-priv-flags ethX
312 ethtool --set-priv-flags ethX mdd-auto-reset-vf [on|off]
315 ---------------------
320 dmesg -n 8
325 ------------
342 /etc/sysconfig/network-scripts/ifcfg-eth<x> // for RHEL
353 -------
360 ----------------------------------------------------
361 -n --show-nfc
364 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
367 -N --config-nfc
370 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r...
380 ------------------------------
382 between copper-based adapters and fiber-based adapters.
385 connections will attempt to auto-negotiate with its link partner to determine
387 using auto-negotiation, you may need to manually configure the adapter and link
390 support auto-negotiation or one that has been forced to a specific speed or
407 An Intel(R) Ethernet Network Adapter using fiber-based connections, however,
408 will not attempt to auto-negotiate with its link partner since those adapters
412 ----
418 ------------
433 ethtool -A eth? rx <on|off> tx <on|off>
435 Note: This command only enables or disables Flow Control if auto-negotiation is
436 disabled. If auto-negotiation is enabled, this command changes the parameters
437 used for auto-negotiation with the link partner.
439 To enable or disable auto-negotiation::
441 ethtool -s eth? autoneg <on|off>
443 Note: Flow Control auto-negotiation is part of link auto-negotiation. Depending
444 on your device, you may not be able to change the auto-negotiation setting.
447 -------------
448 Allows you to set the hash bytes per flow type and any combination of one or
453 # ethtool -N <dev> rx-flow-hash <type> <option>
466 MAC and VLAN anti-spoofing feature
467 ----------------------------------
475 ------------------------------------------------------------
478 "ethtool -T <netdev name>" to get a definitive list of PTP capabilities
482 ---------------------------
501 --------------------------------------
514 Multiple Functions per Port
515 ---------------------------
517 multiple functions on a single physical port. Configure these functions through
521 a percentage of the full physical port link speed, that the partition will
526 1 to ((100 minus # of partitions on the physical port) plus 1)
527 For example, if a physical port has 4 partitions, the range would be:
528 1 to ((100 - 4) + 1 = 97)
531 allocated to the partition as a percentage of the full physical port link
532 speed. The accepted range of values is 1-100. The value is used as a limiter,
534 of a port's bandwidth (should it be available). The sum of all the values for
535 Maximum Bandwidth is not restricted, because no more than 100% of a port's
539 per Port (MFP) and SR-IOV are enabled. An error from i40e is logged that says
544 --------------------------
552 Adapter firmware implements LLDP and DCBX protocol agents as per 802.1AB and
557 NOTE: Firmware LLDP can be disabled by setting the private flag disable-fw-lldp.
559 The i40e driver implements the DCB netlink interface layer to allow user-space
560 to communicate with the driver and query DCB configuration for the port.
568 -----------------------
569 :Valid Range: 0-235 (0=no limit)
577 # ethtool -C ethX rx-usecs-high N
579 The range of 0-235 microseconds provides an effective range of 4,310 to 250,000
580 interrupts per second. The value of rx-usecs-high can be set independently of
581 rx-usecs and tx-usecs in the same ethtool command, and is also independent of
583 granularity in 4-microsecond intervals, so adjacent values may result in the
588 # ethtool -C ethX adaptive-rx off adaptive-tx off rx-usecs-high 20 rx-usecs \
589 5 tx-usecs 5
593 However, instead of resulting in as many as 200,000 interrupts per second, it
594 limits total interrupts per second to 50,000 via the rx-usecs-high parameter.
607 ------------------------
611 for file in `ls /sys/class/net/<ethX>/queues/tx-*/xps_cpus`;
622 Non-virtualized Environments
623 ----------------------------
628 - The following settings will distribute the IRQs across all the cores evenly::
630 # scripts/set_irq_affinity -x all <interface1> , [ <interface2>, ... ]
632 - The following settings will distribute the IRQs across all the cores that are
635 # scripts/set_irq_affinity -x local <interface1> ,[ <interface2>, ... ]
639 For IP Forwarding: Disable Adaptive ITR and lower Rx and Tx interrupts per
642 - Setting rx-usecs and tx-usecs to 125 will limit interrupts to about 8000
643 interrupts per second per queue.
647 # ethtool -C <interface> adaptive-rx off adaptive-tx off rx-usecs 125 \
648 tx-usecs 125
651 per queue using ethtool.
653 - Setting rx-usecs and tx-usecs to 250 will limit interrupts to about 4000
654 interrupts per second per queue.
658 # ethtool -C <interface> adaptive-rx off adaptive-tx off rx-usecs 250 \
659 tx-usecs 250
666 # ethtool -C <interface> adaptive-rx off adaptive-tx off rx-usecs 0 \
667 tx-usecs 0
670 -------------------------------
673 and allow Tx traffic to be rate limited per application. Follow the steps below
676 1. Create traffic classes (TCs). Maximum of 8 TCs can be created per interface.
689 sets priorities 0-3 to use tc0 and 4-7 to use tc1)
700 Totals must be equal or less than port speed.
703 monitoring tools such as `ifstat` or `sar -n DEV [interval] [number of samples]`
707 # ethtool -K <interface> hw-tc-offload on
714 - Run all tc commands from the iproute2 <pathtoiproute2>/tc/ directory.
715 - ADq is not compatible with cloud filters.
716 - Setting up channels via ethtool (ethtool -L) is not supported when the
718 - You must have iproute2 latest version
719 - NVM version 6.01 or later is required.
720 - ADq cannot be enabled when any the following features are enabled: Data
721 Center Bridging (DCB), Multiple Functions per Port (MFP), or Sideband
723 - If another driver (for example, DPDK) has set cloud filters, you cannot
725 - Tunnel filters are not supported in ADq. If encapsulated packets do
726 arrive in non-tunnel mode, filtering will be done on the inner headers.
727 For example, for VXLAN traffic in non-tunnel mode, PCTYPE is identified
730 - If a TC filter on a PF matches traffic over a VF (on the PF), that
734 - If traffic matches multiple TC filters that point to different TCs,
749 * SR-IOV
752 * Auto-media detect
755 ----------------------------------------------------------------
762 "multi-driver" module parameter may mitigate some of the issues.
765 ---------------------------------------------------
778 to intel-wired-lan@lists.osuosl.org.