1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright(c) 2010-2016 Intel Corporation. 3 4.. _testpmd_runtime: 5 6Testpmd Runtime Functions 7========================= 8 9Where the testpmd application is started in interactive mode, (``-i|--interactive``), 10it displays a prompt that can be used to start and stop forwarding, 11configure the application, display statistics (including the extended NIC 12statistics aka xstats) , set the Flow Director and other tasks:: 13 14 testpmd> 15 16The testpmd prompt has some, limited, readline support. 17Common bash command-line functions such as ``Ctrl+a`` and ``Ctrl+e`` to go to the start and end of the prompt line are supported 18as well as access to the command history via the up-arrow. 19 20There is also support for tab completion. 21If you type a partial command and hit ``<TAB>`` you get a list of the available completions: 22 23.. code-block:: console 24 25 testpmd> show port <TAB> 26 27 info [Mul-choice STRING]: show|clear port info|stats|xstats|fdir|stat_qmap|dcb_tc|cap X 28 info [Mul-choice STRING]: show|clear port info|stats|xstats|fdir|stat_qmap|dcb_tc|cap all 29 stats [Mul-choice STRING]: show|clear port info|stats|xstats|fdir|stat_qmap|dcb_tc|cap X 30 stats [Mul-choice STRING]: show|clear port info|stats|xstats|fdir|stat_qmap|dcb_tc|cap all 31 ... 32 33 34.. note:: 35 36 Some examples in this document are too long to fit on one line are are shown wrapped at `"\\"` for display purposes:: 37 38 testpmd> set flow_ctrl rx (on|off) tx (on|off) (high_water) (low_water) \ 39 (pause_time) (send_xon) (port_id) 40 41In the real ``testpmd>`` prompt these commands should be on a single line. 42 43Help Functions 44-------------- 45 46The testpmd has on-line help for the functions that are available at runtime. 47These are divided into sections and can be accessed using help, help section or help all: 48 49.. code-block:: console 50 51 testpmd> help 52 53 help control : Start and stop forwarding. 54 help display : Displaying port, stats and config information. 55 help config : Configuration information. 56 help ports : Configuring ports. 57 help registers : Reading and setting port registers. 58 help filters : Filters configuration help. 59 help all : All of the above sections. 60 61 62Command File Functions 63---------------------- 64 65To facilitate loading large number of commands or to avoid cutting and pasting where not 66practical or possible testpmd supports alternative methods for executing commands. 67 68* If started with the ``--cmdline-file=FILENAME`` command line argument testpmd 69 will execute all CLI commands contained within the file immediately before 70 starting packet forwarding or entering interactive mode. 71 72.. code-block:: console 73 74 ./testpmd -n4 -r2 ... -- -i --cmdline-file=/home/ubuntu/flow-create-commands.txt 75 Interactive-mode selected 76 CLI commands to be read from /home/ubuntu/flow-create-commands.txt 77 Configuring Port 0 (socket 0) 78 Port 0: 7C:FE:90:CB:74:CE 79 Configuring Port 1 (socket 0) 80 Port 1: 7C:FE:90:CB:74:CA 81 Checking link statuses... 82 Port 0 Link Up - speed 10000 Mbps - full-duplex 83 Port 1 Link Up - speed 10000 Mbps - full-duplex 84 Done 85 Flow rule #0 created 86 Flow rule #1 created 87 ... 88 ... 89 Flow rule #498 created 90 Flow rule #499 created 91 Read all CLI commands from /home/ubuntu/flow-create-commands.txt 92 testpmd> 93 94 95* At run-time additional commands can be loaded in bulk by invoking the ``load FILENAME`` 96 command. 97 98.. code-block:: console 99 100 testpmd> load /home/ubuntu/flow-create-commands.txt 101 Flow rule #0 created 102 Flow rule #1 created 103 ... 104 ... 105 Flow rule #498 created 106 Flow rule #499 created 107 Read all CLI commands from /home/ubuntu/flow-create-commands.txt 108 testpmd> 109 110 111In all cases output from any included command will be displayed as standard output. 112Execution will continue until the end of the file is reached regardless of 113whether any errors occur. The end user must examine the output to determine if 114any failures occurred. 115 116 117Control Functions 118----------------- 119 120start 121~~~~~ 122 123Start packet forwarding with current configuration:: 124 125 testpmd> start 126 127start tx_first 128~~~~~~~~~~~~~~ 129 130Start packet forwarding with current configuration after sending specified number of bursts of packets:: 131 132 testpmd> start tx_first (""|burst_num) 133 134The default burst number is 1 when ``burst_num`` not presented. 135 136stop 137~~~~ 138 139Stop packet forwarding, and display accumulated statistics:: 140 141 testpmd> stop 142 143quit 144~~~~ 145 146Quit to prompt:: 147 148 testpmd> quit 149 150 151Display Functions 152----------------- 153 154The functions in the following sections are used to display information about the 155testpmd configuration or the NIC status. 156 157show port 158~~~~~~~~~ 159 160Display information for a given port or all ports:: 161 162 testpmd> show port (info|summary|stats|xstats|fdir|stat_qmap|dcb_tc|cap) (port_id|all) 163 164The available information categories are: 165 166* ``info``: General port information such as MAC address. 167 168* ``summary``: Brief port summary such as Device Name, Driver Name etc. 169 170* ``stats``: RX/TX statistics. 171 172* ``xstats``: RX/TX extended NIC statistics. 173 174* ``fdir``: Flow Director information and statistics. 175 176* ``stat_qmap``: Queue statistics mapping. 177 178* ``dcb_tc``: DCB information such as TC mapping. 179 180* ``cap``: Supported offload capabilities. 181 182For example: 183 184.. code-block:: console 185 186 testpmd> show port info 0 187 188 ********************* Infos for port 0 ********************* 189 190 MAC address: XX:XX:XX:XX:XX:XX 191 Connect to socket: 0 192 memory allocation on the socket: 0 193 Link status: up 194 Link speed: 40000 Mbps 195 Link duplex: full-duplex 196 Promiscuous mode: enabled 197 Allmulticast mode: disabled 198 Maximum number of MAC addresses: 64 199 Maximum number of MAC addresses of hash filtering: 0 200 VLAN offload: 201 strip on 202 filter on 203 qinq(extend) off 204 Redirection table size: 512 205 Supported flow types: 206 ipv4-frag 207 ipv4-tcp 208 ipv4-udp 209 ipv4-sctp 210 ipv4-other 211 ipv6-frag 212 ipv6-tcp 213 ipv6-udp 214 ipv6-sctp 215 ipv6-other 216 l2_payload 217 port 218 vxlan 219 geneve 220 nvgre 221 222show port rss reta 223~~~~~~~~~~~~~~~~~~ 224 225Display the rss redirection table entry indicated by masks on port X:: 226 227 testpmd> show port (port_id) rss reta (size) (mask0, mask1...) 228 229size is used to indicate the hardware supported reta size 230 231show port rss-hash 232~~~~~~~~~~~~~~~~~~ 233 234Display the RSS hash functions and RSS hash key of a port:: 235 236 testpmd> show port (port_id) rss-hash [key] 237 238clear port 239~~~~~~~~~~ 240 241Clear the port statistics for a given port or for all ports:: 242 243 testpmd> clear port (info|stats|xstats|fdir|stat_qmap) (port_id|all) 244 245For example:: 246 247 testpmd> clear port stats all 248 249show (rxq|txq) 250~~~~~~~~~~~~~~ 251 252Display information for a given port's RX/TX queue:: 253 254 testpmd> show (rxq|txq) info (port_id) (queue_id) 255 256show config 257~~~~~~~~~~~ 258 259Displays the configuration of the application. 260The configuration comes from the command-line, the runtime or the application defaults:: 261 262 testpmd> show config (rxtx|cores|fwd|txpkts) 263 264The available information categories are: 265 266* ``rxtx``: RX/TX configuration items. 267 268* ``cores``: List of forwarding cores. 269 270* ``fwd``: Packet forwarding configuration. 271 272* ``txpkts``: Packets to TX configuration. 273 274For example: 275 276.. code-block:: console 277 278 testpmd> show config rxtx 279 280 io packet forwarding - CRC stripping disabled - packets/burst=16 281 nb forwarding cores=2 - nb forwarding ports=1 282 RX queues=1 - RX desc=128 - RX free threshold=0 283 RX threshold registers: pthresh=8 hthresh=8 wthresh=4 284 TX queues=1 - TX desc=512 - TX free threshold=0 285 TX threshold registers: pthresh=36 hthresh=0 wthresh=0 286 TX RS bit threshold=0 - TXQ flags=0x0 287 288set fwd 289~~~~~~~ 290 291Set the packet forwarding mode:: 292 293 testpmd> set fwd (io|mac|macswap|flowgen| \ 294 rxonly|txonly|csum|icmpecho|noisy) (""|retry) 295 296``retry`` can be specified for forwarding engines except ``rx_only``. 297 298The available information categories are: 299 300* ``io``: Forwards packets "as-is" in I/O mode. 301 This is the fastest possible forwarding operation as it does not access packets data. 302 This is the default mode. 303 304* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them. 305 Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination 306 address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or 307 'eth-peer-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address. 308 309* ``macswap``: MAC swap forwarding mode. 310 Swaps the source and the destination Ethernet addresses of packets before forwarding them. 311 312* ``flowgen``: Multi-flow generation mode. 313 Originates a number of flows (with varying destination IP addresses), and terminate receive traffic. 314 315* ``rxonly``: Receives packets but doesn't transmit them. 316 317* ``txonly``: Generates and transmits packets without receiving any. 318 319* ``csum``: Changes the checksum field with hardware or software methods depending on the offload flags on the packet. 320 321* ``icmpecho``: Receives a burst of packets, lookup for IMCP echo requests and, if any, send back ICMP echo replies. 322 323* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. Requires ``CONFIG_RTE_LIBRTE_IEEE1588=y``. 324 325* ``softnic``: Demonstrates the softnic forwarding operation. In this mode, packet forwarding is 326 similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``. 327 328* ``noisy``: Noisy neighbour simulation. 329 Simulate more realistic behavior of a guest machine engaged in receiving 330 and sending packets performing Virtual Network Function (VNF). 331 332Example:: 333 334 testpmd> set fwd rxonly 335 336 Set rxonly packet forwarding mode 337 338 339read rxd 340~~~~~~~~ 341 342Display an RX descriptor for a port RX queue:: 343 344 testpmd> read rxd (port_id) (queue_id) (rxd_id) 345 346For example:: 347 348 testpmd> read rxd 0 0 4 349 0x0000000B - 0x001D0180 / 0x0000000B - 0x001D0180 350 351read txd 352~~~~~~~~ 353 354Display a TX descriptor for a port TX queue:: 355 356 testpmd> read txd (port_id) (queue_id) (txd_id) 357 358For example:: 359 360 testpmd> read txd 0 0 4 361 0x00000001 - 0x24C3C440 / 0x000F0000 - 0x2330003C 362 363ddp get list 364~~~~~~~~~~~~ 365 366Get loaded dynamic device personalization (DDP) package info list:: 367 368 testpmd> ddp get list (port_id) 369 370ddp get info 371~~~~~~~~~~~~ 372 373Display information about dynamic device personalization (DDP) profile:: 374 375 testpmd> ddp get info (profile_path) 376 377show vf stats 378~~~~~~~~~~~~~ 379 380Display VF statistics:: 381 382 testpmd> show vf stats (port_id) (vf_id) 383 384clear vf stats 385~~~~~~~~~~~~~~ 386 387Reset VF statistics:: 388 389 testpmd> clear vf stats (port_id) (vf_id) 390 391show port pctype mapping 392~~~~~~~~~~~~~~~~~~~~~~~~ 393 394List all items from the pctype mapping table:: 395 396 testpmd> show port (port_id) pctype mapping 397 398show rx offloading capabilities 399~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 400 401List all per queue and per port Rx offloading capabilities of a port:: 402 403 testpmd> show port (port_id) rx_offload capabilities 404 405show rx offloading configuration 406~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 407 408List port level and all queue level Rx offloading configuration:: 409 410 testpmd> show port (port_id) rx_offload configuration 411 412show tx offloading capabilities 413~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 414 415List all per queue and per port Tx offloading capabilities of a port:: 416 417 testpmd> show port (port_id) tx_offload capabilities 418 419show tx offloading configuration 420~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 421 422List port level and all queue level Tx offloading configuration:: 423 424 testpmd> show port (port_id) tx_offload configuration 425 426show tx metadata setting 427~~~~~~~~~~~~~~~~~~~~~~~~ 428 429Show Tx metadata value set for a specific port:: 430 431 testpmd> show port (port_id) tx_metadata 432 433Configuration Functions 434----------------------- 435 436The testpmd application can be configured from the runtime as well as from the command-line. 437 438This section details the available configuration functions that are available. 439 440.. note:: 441 442 Configuration changes only become active when forwarding is started/restarted. 443 444set default 445~~~~~~~~~~~ 446 447Reset forwarding to the default configuration:: 448 449 testpmd> set default 450 451set verbose 452~~~~~~~~~~~ 453 454Set the debug verbosity level:: 455 456 testpmd> set verbose (level) 457 458Available levels are as following: 459 460* ``0`` silent except for error. 461* ``1`` fully verbose except for Tx packets. 462* ``2`` fully verbose except for Rx packets. 463* ``> 2`` fully verbose. 464 465set log 466~~~~~~~ 467 468Set the log level for a log type:: 469 470 testpmd> set log global|(type) (level) 471 472Where: 473 474* ``type`` is the log name. 475 476* ``level`` is the log level. 477 478For example, to change the global log level:: 479 testpmd> set log global (level) 480 481Regexes can also be used for type. To change log level of user1, user2 and user3:: 482 testpmd> set log user[1-3] (level) 483 484set nbport 485~~~~~~~~~~ 486 487Set the number of ports used by the application: 488 489set nbport (num) 490 491This is equivalent to the ``--nb-ports`` command-line option. 492 493set nbcore 494~~~~~~~~~~ 495 496Set the number of cores used by the application:: 497 498 testpmd> set nbcore (num) 499 500This is equivalent to the ``--nb-cores`` command-line option. 501 502.. note:: 503 504 The number of cores used must not be greater than number of ports used multiplied by the number of queues per port. 505 506set coremask 507~~~~~~~~~~~~ 508 509Set the forwarding cores hexadecimal mask:: 510 511 testpmd> set coremask (mask) 512 513This is equivalent to the ``--coremask`` command-line option. 514 515.. note:: 516 517 The master lcore is reserved for command line parsing only and cannot be masked on for packet forwarding. 518 519set portmask 520~~~~~~~~~~~~ 521 522Set the forwarding ports hexadecimal mask:: 523 524 testpmd> set portmask (mask) 525 526This is equivalent to the ``--portmask`` command-line option. 527 528set burst 529~~~~~~~~~ 530 531Set number of packets per burst:: 532 533 testpmd> set burst (num) 534 535This is equivalent to the ``--burst command-line`` option. 536 537When retry is enabled, the transmit delay time and number of retries can also be set:: 538 539 testpmd> set burst tx delay (microseconds) retry (num) 540 541set txpkts 542~~~~~~~~~~ 543 544Set the length of each segment of the TX-ONLY packets or length of packet for FLOWGEN mode:: 545 546 testpmd> set txpkts (x[,y]*) 547 548Where x[,y]* represents a CSV list of values, without white space. 549 550set txsplit 551~~~~~~~~~~~ 552 553Set the split policy for the TX packets, applicable for TX-ONLY and CSUM forwarding modes:: 554 555 testpmd> set txsplit (off|on|rand) 556 557Where: 558 559* ``off`` disable packet copy & split for CSUM mode. 560 561* ``on`` split outgoing packet into multiple segments. Size of each segment 562 and number of segments per packet is determined by ``set txpkts`` command 563 (see above). 564 565* ``rand`` same as 'on', but number of segments per each packet is a random value between 1 and total number of segments. 566 567set corelist 568~~~~~~~~~~~~ 569 570Set the list of forwarding cores:: 571 572 testpmd> set corelist (x[,y]*) 573 574For example, to change the forwarding cores: 575 576.. code-block:: console 577 578 testpmd> set corelist 3,1 579 testpmd> show config fwd 580 581 io packet forwarding - ports=2 - cores=2 - streams=2 - NUMA support disabled 582 Logical Core 3 (socket 0) forwards packets on 1 streams: 583 RX P=0/Q=0 (socket 0) -> TX P=1/Q=0 (socket 0) peer=02:00:00:00:00:01 584 Logical Core 1 (socket 0) forwards packets on 1 streams: 585 RX P=1/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00 586 587.. note:: 588 589 The cores are used in the same order as specified on the command line. 590 591set portlist 592~~~~~~~~~~~~ 593 594Set the list of forwarding ports:: 595 596 testpmd> set portlist (x[,y]*) 597 598For example, to change the port forwarding: 599 600.. code-block:: console 601 602 testpmd> set portlist 0,2,1,3 603 testpmd> show config fwd 604 605 io packet forwarding - ports=4 - cores=1 - streams=4 606 Logical Core 3 (socket 0) forwards packets on 4 streams: 607 RX P=0/Q=0 (socket 0) -> TX P=2/Q=0 (socket 0) peer=02:00:00:00:00:01 608 RX P=2/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00 609 RX P=1/Q=0 (socket 0) -> TX P=3/Q=0 (socket 0) peer=02:00:00:00:00:03 610 RX P=3/Q=0 (socket 0) -> TX P=1/Q=0 (socket 0) peer=02:00:00:00:00:02 611 612set port setup on 613~~~~~~~~~~~~~~~~~ 614 615Select how to retrieve new ports created after "port attach" command:: 616 617 testpmd> set port setup on (iterator|event) 618 619For each new port, a setup is done. 620It will find the probed ports via RTE_ETH_FOREACH_MATCHING_DEV loop 621in iterator mode, or via RTE_ETH_EVENT_NEW in event mode. 622 623set tx loopback 624~~~~~~~~~~~~~~~ 625 626Enable/disable tx loopback:: 627 628 testpmd> set tx loopback (port_id) (on|off) 629 630set drop enable 631~~~~~~~~~~~~~~~ 632 633set drop enable bit for all queues:: 634 635 testpmd> set all queues drop (port_id) (on|off) 636 637set split drop enable (for VF) 638~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 639 640set split drop enable bit for VF from PF:: 641 642 testpmd> set vf split drop (port_id) (vf_id) (on|off) 643 644set mac antispoof (for VF) 645~~~~~~~~~~~~~~~~~~~~~~~~~~ 646 647Set mac antispoof for a VF from the PF:: 648 649 testpmd> set vf mac antispoof (port_id) (vf_id) (on|off) 650 651set macsec offload 652~~~~~~~~~~~~~~~~~~ 653 654Enable/disable MACsec offload:: 655 656 testpmd> set macsec offload (port_id) on encrypt (on|off) replay-protect (on|off) 657 testpmd> set macsec offload (port_id) off 658 659set macsec sc 660~~~~~~~~~~~~~ 661 662Configure MACsec secure connection (SC):: 663 664 testpmd> set macsec sc (tx|rx) (port_id) (mac) (pi) 665 666.. note:: 667 668 The pi argument is ignored for tx. 669 Check the NIC Datasheet for hardware limits. 670 671set macsec sa 672~~~~~~~~~~~~~ 673 674Configure MACsec secure association (SA):: 675 676 testpmd> set macsec sa (tx|rx) (port_id) (idx) (an) (pn) (key) 677 678.. note:: 679 680 The IDX value must be 0 or 1. 681 Check the NIC Datasheet for hardware limits. 682 683set broadcast mode (for VF) 684~~~~~~~~~~~~~~~~~~~~~~~~~~~ 685 686Set broadcast mode for a VF from the PF:: 687 688 testpmd> set vf broadcast (port_id) (vf_id) (on|off) 689 690vlan set strip 691~~~~~~~~~~~~~~ 692 693Set the VLAN strip on a port:: 694 695 testpmd> vlan set strip (on|off) (port_id) 696 697vlan set stripq 698~~~~~~~~~~~~~~~ 699 700Set the VLAN strip for a queue on a port:: 701 702 testpmd> vlan set stripq (on|off) (port_id,queue_id) 703 704vlan set stripq (for VF) 705~~~~~~~~~~~~~~~~~~~~~~~~ 706 707Set VLAN strip for all queues in a pool for a VF from the PF:: 708 709 testpmd> set vf vlan stripq (port_id) (vf_id) (on|off) 710 711vlan set insert (for VF) 712~~~~~~~~~~~~~~~~~~~~~~~~ 713 714Set VLAN insert for a VF from the PF:: 715 716 testpmd> set vf vlan insert (port_id) (vf_id) (vlan_id) 717 718vlan set tag (for VF) 719~~~~~~~~~~~~~~~~~~~~~ 720 721Set VLAN tag for a VF from the PF:: 722 723 testpmd> set vf vlan tag (port_id) (vf_id) (on|off) 724 725vlan set antispoof (for VF) 726~~~~~~~~~~~~~~~~~~~~~~~~~~~ 727 728Set VLAN antispoof for a VF from the PF:: 729 730 testpmd> set vf vlan antispoof (port_id) (vf_id) (on|off) 731 732vlan set filter 733~~~~~~~~~~~~~~~ 734 735Set the VLAN filter on a port:: 736 737 testpmd> vlan set filter (on|off) (port_id) 738 739vlan set qinq 740~~~~~~~~~~~~~ 741 742Set the VLAN QinQ (extended queue in queue) on for a port:: 743 744 testpmd> vlan set qinq (on|off) (port_id) 745 746vlan set tpid 747~~~~~~~~~~~~~ 748 749Set the inner or outer VLAN TPID for packet filtering on a port:: 750 751 testpmd> vlan set (inner|outer) tpid (value) (port_id) 752 753.. note:: 754 755 TPID value must be a 16-bit number (value <= 65536). 756 757rx_vlan add 758~~~~~~~~~~~ 759 760Add a VLAN ID, or all identifiers, to the set of VLAN identifiers filtered by port ID:: 761 762 testpmd> rx_vlan add (vlan_id|all) (port_id) 763 764.. note:: 765 766 VLAN filter must be set on that port. VLAN ID < 4096. 767 Depending on the NIC used, number of vlan_ids may be limited to the maximum entries 768 in VFTA table. This is important if enabling all vlan_ids. 769 770rx_vlan rm 771~~~~~~~~~~ 772 773Remove a VLAN ID, or all identifiers, from the set of VLAN identifiers filtered by port ID:: 774 775 testpmd> rx_vlan rm (vlan_id|all) (port_id) 776 777rx_vlan add (for VF) 778~~~~~~~~~~~~~~~~~~~~ 779 780Add a VLAN ID, to the set of VLAN identifiers filtered for VF(s) for port ID:: 781 782 testpmd> rx_vlan add (vlan_id) port (port_id) vf (vf_mask) 783 784rx_vlan rm (for VF) 785~~~~~~~~~~~~~~~~~~~ 786 787Remove a VLAN ID, from the set of VLAN identifiers filtered for VF(s) for port ID:: 788 789 testpmd> rx_vlan rm (vlan_id) port (port_id) vf (vf_mask) 790 791tunnel_filter add 792~~~~~~~~~~~~~~~~~ 793 794Add a tunnel filter on a port:: 795 796 testpmd> tunnel_filter add (port_id) (outer_mac) (inner_mac) (ip_addr) \ 797 (inner_vlan) (vxlan|nvgre|ipingre) (imac-ivlan|imac-ivlan-tenid|\ 798 imac-tenid|imac|omac-imac-tenid|oip|iip) (tenant_id) (queue_id) 799 800The available information categories are: 801 802* ``vxlan``: Set tunnel type as VXLAN. 803 804* ``nvgre``: Set tunnel type as NVGRE. 805 806* ``ipingre``: Set tunnel type as IP-in-GRE. 807 808* ``imac-ivlan``: Set filter type as Inner MAC and VLAN. 809 810* ``imac-ivlan-tenid``: Set filter type as Inner MAC, VLAN and tenant ID. 811 812* ``imac-tenid``: Set filter type as Inner MAC and tenant ID. 813 814* ``imac``: Set filter type as Inner MAC. 815 816* ``omac-imac-tenid``: Set filter type as Outer MAC, Inner MAC and tenant ID. 817 818* ``oip``: Set filter type as Outer IP. 819 820* ``iip``: Set filter type as Inner IP. 821 822Example:: 823 824 testpmd> tunnel_filter add 0 68:05:CA:28:09:82 00:00:00:00:00:00 \ 825 192.168.2.2 0 ipingre oip 1 1 826 827 Set an IP-in-GRE tunnel on port 0, and the filter type is Outer IP. 828 829tunnel_filter remove 830~~~~~~~~~~~~~~~~~~~~ 831 832Remove a tunnel filter on a port:: 833 834 testpmd> tunnel_filter rm (port_id) (outer_mac) (inner_mac) (ip_addr) \ 835 (inner_vlan) (vxlan|nvgre|ipingre) (imac-ivlan|imac-ivlan-tenid|\ 836 imac-tenid|imac|omac-imac-tenid|oip|iip) (tenant_id) (queue_id) 837 838rx_vxlan_port add 839~~~~~~~~~~~~~~~~~ 840 841Add an UDP port for VXLAN packet filter on a port:: 842 843 testpmd> rx_vxlan_port add (udp_port) (port_id) 844 845rx_vxlan_port remove 846~~~~~~~~~~~~~~~~~~~~ 847 848Remove an UDP port for VXLAN packet filter on a port:: 849 850 testpmd> rx_vxlan_port rm (udp_port) (port_id) 851 852tx_vlan set 853~~~~~~~~~~~ 854 855Set hardware insertion of VLAN IDs in packets sent on a port:: 856 857 testpmd> tx_vlan set (port_id) vlan_id[, vlan_id_outer] 858 859For example, set a single VLAN ID (5) insertion on port 0:: 860 861 tx_vlan set 0 5 862 863Or, set double VLAN ID (inner: 2, outer: 3) insertion on port 1:: 864 865 tx_vlan set 1 2 3 866 867 868tx_vlan set pvid 869~~~~~~~~~~~~~~~~ 870 871Set port based hardware insertion of VLAN ID in packets sent on a port:: 872 873 testpmd> tx_vlan set pvid (port_id) (vlan_id) (on|off) 874 875tx_vlan reset 876~~~~~~~~~~~~~ 877 878Disable hardware insertion of a VLAN header in packets sent on a port:: 879 880 testpmd> tx_vlan reset (port_id) 881 882csum set 883~~~~~~~~ 884 885Select hardware or software calculation of the checksum when 886transmitting a packet using the ``csum`` forwarding engine:: 887 888 testpmd> csum set (ip|udp|tcp|sctp|outer-ip|outer-udp) (hw|sw) (port_id) 889 890Where: 891 892* ``ip|udp|tcp|sctp`` always relate to the inner layer. 893 894* ``outer-ip`` relates to the outer IP layer (only for IPv4) in the case where the packet is recognized 895 as a tunnel packet by the forwarding engine (vxlan, gre and ipip are 896 supported). See also the ``csum parse-tunnel`` command. 897 898* ``outer-udp`` relates to the outer UDP layer in the case where the packet is recognized 899 as a tunnel packet by the forwarding engine (vxlan, vxlan-gpe are 900 supported). See also the ``csum parse-tunnel`` command. 901 902.. note:: 903 904 Check the NIC Datasheet for hardware limits. 905 906RSS queue region 907~~~~~~~~~~~~~~~~ 908 909Set RSS queue region span on a port:: 910 911 testpmd> set port (port_id) queue-region region_id (value) \ 912 queue_start_index (value) queue_num (value) 913 914Set flowtype mapping on a RSS queue region on a port:: 915 916 testpmd> set port (port_id) queue-region region_id (value) flowtype (value) 917 918where: 919 920* For the flowtype(pctype) of packet,the specific index for each type has 921 been defined in file i40e_type.h as enum i40e_filter_pctype. 922 923Set user priority mapping on a RSS queue region on a port:: 924 925 testpmd> set port (port_id) queue-region UP (value) region_id (value) 926 927Flush all queue region related configuration on a port:: 928 929 testpmd> set port (port_id) queue-region flush (on|off) 930 931where: 932 933* "on"is just an enable function which server for other configuration, 934 it is for all configuration about queue region from up layer, 935 at first will only keep in DPDK softwarestored in driver, 936 only after "flush on", it commit all configuration to HW. 937 "off" is just clean all configuration about queue region just now, 938 and restore all to DPDK i40e driver default config when start up. 939 940Show all queue region related configuration info on a port:: 941 942 testpmd> show port (port_id) queue-region 943 944.. note:: 945 946 Queue region only support on PF by now, so these command is 947 only for configuration of queue region on PF port. 948 949csum parse-tunnel 950~~~~~~~~~~~~~~~~~ 951 952Define how tunneled packets should be handled by the csum forward 953engine:: 954 955 testpmd> csum parse-tunnel (on|off) (tx_port_id) 956 957If enabled, the csum forward engine will try to recognize supported 958tunnel headers (vxlan, gre, ipip). 959 960If disabled, treat tunnel packets as non-tunneled packets (a inner 961header is handled as a packet payload). 962 963.. note:: 964 965 The port argument is the TX port like in the ``csum set`` command. 966 967Example: 968 969Consider a packet in packet like the following:: 970 971 eth_out/ipv4_out/udp_out/vxlan/eth_in/ipv4_in/tcp_in 972 973* If parse-tunnel is enabled, the ``ip|udp|tcp|sctp`` parameters of ``csum set`` 974 command relate to the inner headers (here ``ipv4_in`` and ``tcp_in``), and the 975 ``outer-ip|outer-udp`` parameter relates to the outer headers (here ``ipv4_out`` and ``udp_out``). 976 977* If parse-tunnel is disabled, the ``ip|udp|tcp|sctp`` parameters of ``csum set`` 978 command relate to the outer headers, here ``ipv4_out`` and ``udp_out``. 979 980csum show 981~~~~~~~~~ 982 983Display tx checksum offload configuration:: 984 985 testpmd> csum show (port_id) 986 987tso set 988~~~~~~~ 989 990Enable TCP Segmentation Offload (TSO) in the ``csum`` forwarding engine:: 991 992 testpmd> tso set (segsize) (port_id) 993 994.. note:: 995 996 Check the NIC datasheet for hardware limits. 997 998tso show 999~~~~~~~~ 1000 1001Display the status of TCP Segmentation Offload:: 1002 1003 testpmd> tso show (port_id) 1004 1005set port - gro 1006~~~~~~~~~~~~~~ 1007 1008Enable or disable GRO in ``csum`` forwarding engine:: 1009 1010 testpmd> set port <port_id> gro on|off 1011 1012If enabled, the csum forwarding engine will perform GRO on the TCP/IPv4 1013packets received from the given port. 1014 1015If disabled, packets received from the given port won't be performed 1016GRO. By default, GRO is disabled for all ports. 1017 1018.. note:: 1019 1020 When enable GRO for a port, TCP/IPv4 packets received from the port 1021 will be performed GRO. After GRO, all merged packets have bad 1022 checksums, since the GRO library doesn't re-calculate checksums for 1023 the merged packets. Therefore, if users want the merged packets to 1024 have correct checksums, please select HW IP checksum calculation and 1025 HW TCP checksum calculation for the port which the merged packets are 1026 transmitted to. 1027 1028show port - gro 1029~~~~~~~~~~~~~~~ 1030 1031Display GRO configuration for a given port:: 1032 1033 testpmd> show port <port_id> gro 1034 1035set gro flush 1036~~~~~~~~~~~~~ 1037 1038Set the cycle to flush the GROed packets from reassembly tables:: 1039 1040 testpmd> set gro flush <cycles> 1041 1042When enable GRO, the csum forwarding engine performs GRO on received 1043packets, and the GROed packets are stored in reassembly tables. Users 1044can use this command to determine when the GROed packets are flushed 1045from the reassembly tables. 1046 1047The ``cycles`` is measured in GRO operation times. The csum forwarding 1048engine flushes the GROed packets from the tables every ``cycles`` GRO 1049operations. 1050 1051By default, the value of ``cycles`` is 1, which means flush GROed packets 1052from the reassembly tables as soon as one GRO operation finishes. The value 1053of ``cycles`` should be in the range of 1 to ``GRO_MAX_FLUSH_CYCLES``. 1054 1055Please note that the large value of ``cycles`` may cause the poor TCP/IP 1056stack performance. Because the GROed packets are delayed to arrive the 1057stack, thus causing more duplicated ACKs and TCP retransmissions. 1058 1059set port - gso 1060~~~~~~~~~~~~~~ 1061 1062Toggle per-port GSO support in ``csum`` forwarding engine:: 1063 1064 testpmd> set port <port_id> gso on|off 1065 1066If enabled, the csum forwarding engine will perform GSO on supported IPv4 1067packets, transmitted on the given port. 1068 1069If disabled, packets transmitted on the given port will not undergo GSO. 1070By default, GSO is disabled for all ports. 1071 1072.. note:: 1073 1074 When GSO is enabled on a port, supported IPv4 packets transmitted on that 1075 port undergo GSO. Afterwards, the segmented packets are represented by 1076 multi-segment mbufs; however, the csum forwarding engine doesn't calculation 1077 of checksums for GSO'd segments in SW. As a result, if users want correct 1078 checksums in GSO segments, they should enable HW checksum calculation for 1079 GSO-enabled ports. 1080 1081 For example, HW checksum calculation for VxLAN GSO'd packets may be enabled 1082 by setting the following options in the csum forwarding engine: 1083 1084 testpmd> csum set outer_ip hw <port_id> 1085 1086 testpmd> csum set ip hw <port_id> 1087 1088 testpmd> csum set tcp hw <port_id> 1089 1090 UDP GSO is the same as IP fragmentation, which treats the UDP header 1091 as the payload and does not modify it during segmentation. That is, 1092 after UDP GSO, only the first output fragment has the original UDP 1093 header. Therefore, users need to enable HW IP checksum calculation 1094 and SW UDP checksum calculation for GSO-enabled ports, if they want 1095 correct checksums for UDP/IPv4 packets. 1096 1097set gso segsz 1098~~~~~~~~~~~~~ 1099 1100Set the maximum GSO segment size (measured in bytes), which includes the 1101packet header and the packet payload for GSO-enabled ports (global):: 1102 1103 testpmd> set gso segsz <length> 1104 1105show port - gso 1106~~~~~~~~~~~~~~~ 1107 1108Display the status of Generic Segmentation Offload for a given port:: 1109 1110 testpmd> show port <port_id> gso 1111 1112mac_addr add 1113~~~~~~~~~~~~ 1114 1115Add an alternative MAC address to a port:: 1116 1117 testpmd> mac_addr add (port_id) (XX:XX:XX:XX:XX:XX) 1118 1119mac_addr remove 1120~~~~~~~~~~~~~~~ 1121 1122Remove a MAC address from a port:: 1123 1124 testpmd> mac_addr remove (port_id) (XX:XX:XX:XX:XX:XX) 1125 1126mac_addr add (for VF) 1127~~~~~~~~~~~~~~~~~~~~~ 1128 1129Add an alternative MAC address for a VF to a port:: 1130 1131 testpmd> mac_add add port (port_id) vf (vf_id) (XX:XX:XX:XX:XX:XX) 1132 1133mac_addr set 1134~~~~~~~~~~~~ 1135 1136Set the default MAC address for a port:: 1137 1138 testpmd> mac_addr set (port_id) (XX:XX:XX:XX:XX:XX) 1139 1140mac_addr set (for VF) 1141~~~~~~~~~~~~~~~~~~~~~ 1142 1143Set the MAC address for a VF from the PF:: 1144 1145 testpmd> set vf mac addr (port_id) (vf_id) (XX:XX:XX:XX:XX:XX) 1146 1147set eth-peer 1148~~~~~~~~~~~~ 1149 1150Set the forwarding peer address for certain port:: 1151 1152 testpmd> set eth-peer (port_id) (perr_addr) 1153 1154This is equivalent to the ``--eth-peer`` command-line option. 1155 1156set port-uta 1157~~~~~~~~~~~~ 1158 1159Set the unicast hash filter(s) on/off for a port:: 1160 1161 testpmd> set port (port_id) uta (XX:XX:XX:XX:XX:XX|all) (on|off) 1162 1163set promisc 1164~~~~~~~~~~~ 1165 1166Set the promiscuous mode on for a port or for all ports. 1167In promiscuous mode packets are not dropped if they aren't for the specified MAC address:: 1168 1169 testpmd> set promisc (port_id|all) (on|off) 1170 1171set allmulti 1172~~~~~~~~~~~~ 1173 1174Set the allmulti mode for a port or for all ports:: 1175 1176 testpmd> set allmulti (port_id|all) (on|off) 1177 1178Same as the ifconfig (8) option. Controls how multicast packets are handled. 1179 1180set promisc (for VF) 1181~~~~~~~~~~~~~~~~~~~~ 1182 1183Set the unicast promiscuous mode for a VF from PF. 1184It's supported by Intel i40e NICs now. 1185In promiscuous mode packets are not dropped if they aren't for the specified MAC address:: 1186 1187 testpmd> set vf promisc (port_id) (vf_id) (on|off) 1188 1189set allmulticast (for VF) 1190~~~~~~~~~~~~~~~~~~~~~~~~~ 1191 1192Set the multicast promiscuous mode for a VF from PF. 1193It's supported by Intel i40e NICs now. 1194In promiscuous mode packets are not dropped if they aren't for the specified MAC address:: 1195 1196 testpmd> set vf allmulti (port_id) (vf_id) (on|off) 1197 1198set tx max bandwidth (for VF) 1199~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1200 1201Set TX max absolute bandwidth (Mbps) for a VF from PF:: 1202 1203 testpmd> set vf tx max-bandwidth (port_id) (vf_id) (max_bandwidth) 1204 1205set tc tx min bandwidth (for VF) 1206~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1207 1208Set all TCs' TX min relative bandwidth (%) for a VF from PF:: 1209 1210 testpmd> set vf tc tx min-bandwidth (port_id) (vf_id) (bw1, bw2, ...) 1211 1212set tc tx max bandwidth (for VF) 1213~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1214 1215Set a TC's TX max absolute bandwidth (Mbps) for a VF from PF:: 1216 1217 testpmd> set vf tc tx max-bandwidth (port_id) (vf_id) (tc_no) (max_bandwidth) 1218 1219set tc strict link priority mode 1220~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1221 1222Set some TCs' strict link priority mode on a physical port:: 1223 1224 testpmd> set tx strict-link-priority (port_id) (tc_bitmap) 1225 1226set tc tx min bandwidth 1227~~~~~~~~~~~~~~~~~~~~~~~ 1228 1229Set all TCs' TX min relative bandwidth (%) globally for all PF and VFs:: 1230 1231 testpmd> set tc tx min-bandwidth (port_id) (bw1, bw2, ...) 1232 1233set flow_ctrl rx 1234~~~~~~~~~~~~~~~~ 1235 1236Set the link flow control parameter on a port:: 1237 1238 testpmd> set flow_ctrl rx (on|off) tx (on|off) (high_water) (low_water) \ 1239 (pause_time) (send_xon) mac_ctrl_frame_fwd (on|off) \ 1240 autoneg (on|off) (port_id) 1241 1242Where: 1243 1244* ``high_water`` (integer): High threshold value to trigger XOFF. 1245 1246* ``low_water`` (integer): Low threshold value to trigger XON. 1247 1248* ``pause_time`` (integer): Pause quota in the Pause frame. 1249 1250* ``send_xon`` (0/1): Send XON frame. 1251 1252* ``mac_ctrl_frame_fwd``: Enable receiving MAC control frames. 1253 1254* ``autoneg``: Change the auto-negotiation parameter. 1255 1256set pfc_ctrl rx 1257~~~~~~~~~~~~~~~ 1258 1259Set the priority flow control parameter on a port:: 1260 1261 testpmd> set pfc_ctrl rx (on|off) tx (on|off) (high_water) (low_water) \ 1262 (pause_time) (priority) (port_id) 1263 1264Where: 1265 1266* ``high_water`` (integer): High threshold value. 1267 1268* ``low_water`` (integer): Low threshold value. 1269 1270* ``pause_time`` (integer): Pause quota in the Pause frame. 1271 1272* ``priority`` (0-7): VLAN User Priority. 1273 1274set stat_qmap 1275~~~~~~~~~~~~~ 1276 1277Set statistics mapping (qmapping 0..15) for RX/TX queue on port:: 1278 1279 testpmd> set stat_qmap (tx|rx) (port_id) (queue_id) (qmapping) 1280 1281For example, to set rx queue 2 on port 0 to mapping 5:: 1282 1283 testpmd>set stat_qmap rx 0 2 5 1284 1285set xstats-hide-zero 1286~~~~~~~~~~~~~~~~~~~~ 1287 1288Set the option to hide zero values for xstats display:: 1289 1290 testpmd> set xstats-hide-zero on|off 1291 1292.. note:: 1293 1294 By default, the zero values are displayed for xstats. 1295 1296set port - rx/tx (for VF) 1297~~~~~~~~~~~~~~~~~~~~~~~~~ 1298 1299Set VF receive/transmit from a port:: 1300 1301 testpmd> set port (port_id) vf (vf_id) (rx|tx) (on|off) 1302 1303set port - mac address filter (for VF) 1304~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1305 1306Add/Remove unicast or multicast MAC addr filter for a VF:: 1307 1308 testpmd> set port (port_id) vf (vf_id) (mac_addr) \ 1309 (exact-mac|exact-mac-vlan|hashmac|hashmac-vlan) (on|off) 1310 1311set port - rx mode(for VF) 1312~~~~~~~~~~~~~~~~~~~~~~~~~~ 1313 1314Set the VF receive mode of a port:: 1315 1316 testpmd> set port (port_id) vf (vf_id) \ 1317 rxmode (AUPE|ROPE|BAM|MPE) (on|off) 1318 1319The available receive modes are: 1320 1321* ``AUPE``: Accepts untagged VLAN. 1322 1323* ``ROPE``: Accepts unicast hash. 1324 1325* ``BAM``: Accepts broadcast packets. 1326 1327* ``MPE``: Accepts all multicast packets. 1328 1329set port - tx_rate (for Queue) 1330~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1331 1332Set TX rate limitation for a queue on a port:: 1333 1334 testpmd> set port (port_id) queue (queue_id) rate (rate_value) 1335 1336set port - tx_rate (for VF) 1337~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1338 1339Set TX rate limitation for queues in VF on a port:: 1340 1341 testpmd> set port (port_id) vf (vf_id) rate (rate_value) queue_mask (queue_mask) 1342 1343set port - mirror rule 1344~~~~~~~~~~~~~~~~~~~~~~ 1345 1346Set pool or vlan type mirror rule for a port:: 1347 1348 testpmd> set port (port_id) mirror-rule (rule_id) \ 1349 (pool-mirror-up|pool-mirror-down|vlan-mirror) \ 1350 (poolmask|vlanid[,vlanid]*) dst-pool (pool_id) (on|off) 1351 1352Set link mirror rule for a port:: 1353 1354 testpmd> set port (port_id) mirror-rule (rule_id) \ 1355 (uplink-mirror|downlink-mirror) dst-pool (pool_id) (on|off) 1356 1357For example to enable mirror traffic with vlan 0,1 to pool 0:: 1358 1359 set port 0 mirror-rule 0 vlan-mirror 0,1 dst-pool 0 on 1360 1361reset port - mirror rule 1362~~~~~~~~~~~~~~~~~~~~~~~~ 1363 1364Reset a mirror rule for a port:: 1365 1366 testpmd> reset port (port_id) mirror-rule (rule_id) 1367 1368set flush_rx 1369~~~~~~~~~~~~ 1370 1371Set the flush on RX streams before forwarding. 1372The default is flush ``on``. 1373Mainly used with PCAP drivers to turn off the default behavior of flushing the first 512 packets on RX streams:: 1374 1375 testpmd> set flush_rx off 1376 1377set bypass mode 1378~~~~~~~~~~~~~~~ 1379 1380Set the bypass mode for the lowest port on bypass enabled NIC:: 1381 1382 testpmd> set bypass mode (normal|bypass|isolate) (port_id) 1383 1384set bypass event 1385~~~~~~~~~~~~~~~~ 1386 1387Set the event required to initiate specified bypass mode for the lowest port on a bypass enabled:: 1388 1389 testpmd> set bypass event (timeout|os_on|os_off|power_on|power_off) \ 1390 mode (normal|bypass|isolate) (port_id) 1391 1392Where: 1393 1394* ``timeout``: Enable bypass after watchdog timeout. 1395 1396* ``os_on``: Enable bypass when OS/board is powered on. 1397 1398* ``os_off``: Enable bypass when OS/board is powered off. 1399 1400* ``power_on``: Enable bypass when power supply is turned on. 1401 1402* ``power_off``: Enable bypass when power supply is turned off. 1403 1404 1405set bypass timeout 1406~~~~~~~~~~~~~~~~~~ 1407 1408Set the bypass watchdog timeout to ``n`` seconds where 0 = instant:: 1409 1410 testpmd> set bypass timeout (0|1.5|2|3|4|8|16|32) 1411 1412show bypass config 1413~~~~~~~~~~~~~~~~~~ 1414 1415Show the bypass configuration for a bypass enabled NIC using the lowest port on the NIC:: 1416 1417 testpmd> show bypass config (port_id) 1418 1419set link up 1420~~~~~~~~~~~ 1421 1422Set link up for a port:: 1423 1424 testpmd> set link-up port (port id) 1425 1426set link down 1427~~~~~~~~~~~~~ 1428 1429Set link down for a port:: 1430 1431 testpmd> set link-down port (port id) 1432 1433E-tag set 1434~~~~~~~~~ 1435 1436Enable E-tag insertion for a VF on a port:: 1437 1438 testpmd> E-tag set insertion on port-tag-id (value) port (port_id) vf (vf_id) 1439 1440Disable E-tag insertion for a VF on a port:: 1441 1442 testpmd> E-tag set insertion off port (port_id) vf (vf_id) 1443 1444Enable/disable E-tag stripping on a port:: 1445 1446 testpmd> E-tag set stripping (on|off) port (port_id) 1447 1448Enable/disable E-tag based forwarding on a port:: 1449 1450 testpmd> E-tag set forwarding (on|off) port (port_id) 1451 1452Add an E-tag forwarding filter on a port:: 1453 1454 testpmd> E-tag set filter add e-tag-id (value) dst-pool (pool_id) port (port_id) 1455 1456Delete an E-tag forwarding filter on a port:: 1457 testpmd> E-tag set filter del e-tag-id (value) port (port_id) 1458 1459ddp add 1460~~~~~~~ 1461 1462Load a dynamic device personalization (DDP) profile and store backup profile:: 1463 1464 testpmd> ddp add (port_id) (profile_path[,backup_profile_path]) 1465 1466ddp del 1467~~~~~~~ 1468 1469Delete a dynamic device personalization profile and restore backup profile:: 1470 1471 testpmd> ddp del (port_id) (backup_profile_path) 1472 1473ptype mapping 1474~~~~~~~~~~~~~ 1475 1476List all items from the ptype mapping table:: 1477 1478 testpmd> ptype mapping get (port_id) (valid_only) 1479 1480Where: 1481 1482* ``valid_only``: A flag indicates if only list valid items(=1) or all itemss(=0). 1483 1484Replace a specific or a group of software defined ptype with a new one:: 1485 1486 testpmd> ptype mapping replace (port_id) (target) (mask) (pkt_type) 1487 1488where: 1489 1490* ``target``: A specific software ptype or a mask to represent a group of software ptypes. 1491 1492* ``mask``: A flag indicate if "target" is a specific software ptype(=0) or a ptype mask(=1). 1493 1494* ``pkt_type``: The new software ptype to replace the old ones. 1495 1496Update hardware defined ptype to software defined packet type mapping table:: 1497 1498 testpmd> ptype mapping update (port_id) (hw_ptype) (sw_ptype) 1499 1500where: 1501 1502* ``hw_ptype``: hardware ptype as the index of the ptype mapping table. 1503 1504* ``sw_ptype``: software ptype as the value of the ptype mapping table. 1505 1506Reset ptype mapping table:: 1507 1508 testpmd> ptype mapping reset (port_id) 1509 1510config per port Rx offloading 1511~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1512 1513Enable or disable a per port Rx offloading on all Rx queues of a port:: 1514 1515 testpmd> port config (port_id) rx_offload (offloading) on|off 1516 1517* ``offloading``: can be any of these offloading capability: 1518 vlan_strip, ipv4_cksum, udp_cksum, tcp_cksum, tcp_lro, 1519 qinq_strip, outer_ipv4_cksum, macsec_strip, 1520 header_split, vlan_filter, vlan_extend, jumbo_frame, 1521 crc_strip, scatter, timestamp, security, keep_crc 1522 1523This command should be run when the port is stopped, or else it will fail. 1524 1525config per queue Rx offloading 1526~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1527 1528Enable or disable a per queue Rx offloading only on a specific Rx queue:: 1529 1530 testpmd> port (port_id) rxq (queue_id) rx_offload (offloading) on|off 1531 1532* ``offloading``: can be any of these offloading capability: 1533 vlan_strip, ipv4_cksum, udp_cksum, tcp_cksum, tcp_lro, 1534 qinq_strip, outer_ipv4_cksum, macsec_strip, 1535 header_split, vlan_filter, vlan_extend, jumbo_frame, 1536 crc_strip, scatter, timestamp, security, keep_crc 1537 1538This command should be run when the port is stopped, or else it will fail. 1539 1540config per port Tx offloading 1541~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1542 1543Enable or disable a per port Tx offloading on all Tx queues of a port:: 1544 1545 testpmd> port config (port_id) tx_offload (offloading) on|off 1546 1547* ``offloading``: can be any of these offloading capability: 1548 vlan_insert, ipv4_cksum, udp_cksum, tcp_cksum, 1549 sctp_cksum, tcp_tso, udp_tso, outer_ipv4_cksum, 1550 qinq_insert, vxlan_tnl_tso, gre_tnl_tso, 1551 ipip_tnl_tso, geneve_tnl_tso, macsec_insert, 1552 mt_lockfree, multi_segs, mbuf_fast_free, security, 1553 match_metadata 1554 1555This command should be run when the port is stopped, or else it will fail. 1556 1557config per queue Tx offloading 1558~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1559 1560Enable or disable a per queue Tx offloading only on a specific Tx queue:: 1561 1562 testpmd> port (port_id) txq (queue_id) tx_offload (offloading) on|off 1563 1564* ``offloading``: can be any of these offloading capability: 1565 vlan_insert, ipv4_cksum, udp_cksum, tcp_cksum, 1566 sctp_cksum, tcp_tso, udp_tso, outer_ipv4_cksum, 1567 qinq_insert, vxlan_tnl_tso, gre_tnl_tso, 1568 ipip_tnl_tso, geneve_tnl_tso, macsec_insert, 1569 mt_lockfree, multi_segs, mbuf_fast_free, security 1570 1571This command should be run when the port is stopped, or else it will fail. 1572 1573Config VXLAN Encap outer layers 1574~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1575 1576Configure the outer layer to encapsulate a packet inside a VXLAN tunnel:: 1577 1578 set vxlan ip-version (ipv4|ipv6) vni (vni) udp-src (udp-src) \ 1579 udp-dst (udp-dst) ip-src (ip-src) ip-dst (ip-dst) eth-src (eth-src) \ 1580 eth-dst (eth-dst) 1581 1582 set vxlan-with-vlan ip-version (ipv4|ipv6) vni (vni) udp-src (udp-src) \ 1583 udp-dst (udp-dst) ip-src (ip-src) ip-dst (ip-dst) vlan-tci (vlan-tci) \ 1584 eth-src (eth-src) eth-dst (eth-dst) 1585 1586Those command will set an internal configuration inside testpmd, any following 1587flow rule using the action vxlan_encap will use the last configuration set. 1588To have a different encapsulation header, one of those commands must be called 1589before the flow rule creation. 1590 1591Config NVGRE Encap outer layers 1592~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1593 1594Configure the outer layer to encapsulate a packet inside a NVGRE tunnel:: 1595 1596 set nvgre ip-version (ipv4|ipv6) tni (tni) ip-src (ip-src) ip-dst (ip-dst) \ 1597 eth-src (eth-src) eth-dst (eth-dst) 1598 set nvgre-with-vlan ip-version (ipv4|ipv6) tni (tni) ip-src (ip-src) \ 1599 ip-dst (ip-dst) vlan-tci (vlan-tci) eth-src (eth-src) eth-dst (eth-dst) 1600 1601Those command will set an internal configuration inside testpmd, any following 1602flow rule using the action nvgre_encap will use the last configuration set. 1603To have a different encapsulation header, one of those commands must be called 1604before the flow rule creation. 1605 1606Config L2 Encap 1607~~~~~~~~~~~~~~~ 1608 1609Configure the l2 to be used when encapsulating a packet with L2:: 1610 1611 set l2_encap ip-version (ipv4|ipv6) eth-src (eth-src) eth-dst (eth-dst) 1612 set l2_encap-with-vlan ip-version (ipv4|ipv6) vlan-tci (vlan-tci) \ 1613 eth-src (eth-src) eth-dst (eth-dst) 1614 1615Those commands will set an internal configuration inside testpmd, any following 1616flow rule using the action l2_encap will use the last configuration set. 1617To have a different encapsulation header, one of those commands must be called 1618before the flow rule creation. 1619 1620Config L2 Decap 1621~~~~~~~~~~~~~~~ 1622 1623Configure the l2 to be removed when decapsulating a packet with L2:: 1624 1625 set l2_decap ip-version (ipv4|ipv6) 1626 set l2_decap-with-vlan ip-version (ipv4|ipv6) 1627 1628Those commands will set an internal configuration inside testpmd, any following 1629flow rule using the action l2_decap will use the last configuration set. 1630To have a different encapsulation header, one of those commands must be called 1631before the flow rule creation. 1632 1633Config MPLSoGRE Encap outer layers 1634~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1635 1636Configure the outer layer to encapsulate a packet inside a MPLSoGRE tunnel:: 1637 1638 set mplsogre_encap ip-version (ipv4|ipv6) label (label) \ 1639 ip-src (ip-src) ip-dst (ip-dst) eth-src (eth-src) eth-dst (eth-dst) 1640 set mplsogre_encap-with-vlan ip-version (ipv4|ipv6) label (label) \ 1641 ip-src (ip-src) ip-dst (ip-dst) vlan-tci (vlan-tci) \ 1642 eth-src (eth-src) eth-dst (eth-dst) 1643 1644Those command will set an internal configuration inside testpmd, any following 1645flow rule using the action mplsogre_encap will use the last configuration set. 1646To have a different encapsulation header, one of those commands must be called 1647before the flow rule creation. 1648 1649Config MPLSoGRE Decap outer layers 1650~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1651 1652Configure the outer layer to decapsulate MPLSoGRE packet:: 1653 1654 set mplsogre_decap ip-version (ipv4|ipv6) 1655 set mplsogre_decap-with-vlan ip-version (ipv4|ipv6) 1656 1657Those command will set an internal configuration inside testpmd, any following 1658flow rule using the action mplsogre_decap will use the last configuration set. 1659To have a different decapsulation header, one of those commands must be called 1660before the flow rule creation. 1661 1662Config MPLSoUDP Encap outer layers 1663~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1664 1665Configure the outer layer to encapsulate a packet inside a MPLSoUDP tunnel:: 1666 1667 set mplsoudp_encap ip-version (ipv4|ipv6) label (label) udp-src (udp-src) \ 1668 udp-dst (udp-dst) ip-src (ip-src) ip-dst (ip-dst) \ 1669 eth-src (eth-src) eth-dst (eth-dst) 1670 set mplsoudp_encap-with-vlan ip-version (ipv4|ipv6) label (label) \ 1671 udp-src (udp-src) udp-dst (udp-dst) ip-src (ip-src) ip-dst (ip-dst) \ 1672 vlan-tci (vlan-tci) eth-src (eth-src) eth-dst (eth-dst) 1673 1674Those command will set an internal configuration inside testpmd, any following 1675flow rule using the action mplsoudp_encap will use the last configuration set. 1676To have a different encapsulation header, one of those commands must be called 1677before the flow rule creation. 1678 1679Config MPLSoUDP Decap outer layers 1680~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1681 1682Configure the outer layer to decapsulate MPLSoUDP packet:: 1683 1684 set mplsoudp_decap ip-version (ipv4|ipv6) 1685 set mplsoudp_decap-with-vlan ip-version (ipv4|ipv6) 1686 1687Those command will set an internal configuration inside testpmd, any following 1688flow rule using the action mplsoudp_decap will use the last configuration set. 1689To have a different decapsulation header, one of those commands must be called 1690before the flow rule creation. 1691 1692Port Functions 1693-------------- 1694 1695The following sections show functions for configuring ports. 1696 1697.. note:: 1698 1699 Port configuration changes only become active when forwarding is started/restarted. 1700 1701port attach 1702~~~~~~~~~~~ 1703 1704Attach a port specified by pci address or virtual device args:: 1705 1706 testpmd> port attach (identifier) 1707 1708To attach a new pci device, the device should be recognized by kernel first. 1709Then it should be moved under DPDK management. 1710Finally the port can be attached to testpmd. 1711 1712For example, to move a pci device using ixgbe under DPDK management: 1713 1714.. code-block:: console 1715 1716 # Check the status of the available devices. 1717 ./usertools/dpdk-devbind.py --status 1718 1719 Network devices using DPDK-compatible driver 1720 ============================================ 1721 <none> 1722 1723 Network devices using kernel driver 1724 =================================== 1725 0000:0a:00.0 '82599ES 10-Gigabit' if=eth2 drv=ixgbe unused= 1726 1727 1728 # Bind the device to igb_uio. 1729 sudo ./usertools/dpdk-devbind.py -b igb_uio 0000:0a:00.0 1730 1731 1732 # Recheck the status of the devices. 1733 ./usertools/dpdk-devbind.py --status 1734 Network devices using DPDK-compatible driver 1735 ============================================ 1736 0000:0a:00.0 '82599ES 10-Gigabit' drv=igb_uio unused= 1737 1738To attach a port created by virtual device, above steps are not needed. 1739 1740For example, to attach a port whose pci address is 0000:0a:00.0. 1741 1742.. code-block:: console 1743 1744 testpmd> port attach 0000:0a:00.0 1745 Attaching a new port... 1746 EAL: PCI device 0000:0a:00.0 on NUMA socket -1 1747 EAL: probe driver: 8086:10fb rte_ixgbe_pmd 1748 EAL: PCI memory mapped at 0x7f83bfa00000 1749 EAL: PCI memory mapped at 0x7f83bfa80000 1750 PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5 1751 PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb 1752 Port 0 is attached. Now total ports is 1 1753 Done 1754 1755For example, to attach a port created by pcap PMD. 1756 1757.. code-block:: console 1758 1759 testpmd> port attach net_pcap0 1760 Attaching a new port... 1761 PMD: Initializing pmd_pcap for net_pcap0 1762 PMD: Creating pcap-backed ethdev on numa socket 0 1763 Port 0 is attached. Now total ports is 1 1764 Done 1765 1766In this case, identifier is ``net_pcap0``. 1767This identifier format is the same as ``--vdev`` format of DPDK applications. 1768 1769For example, to re-attach a bonded port which has been previously detached, 1770the mode and slave parameters must be given. 1771 1772.. code-block:: console 1773 1774 testpmd> port attach net_bond_0,mode=0,slave=1 1775 Attaching a new port... 1776 EAL: Initializing pmd_bond for net_bond_0 1777 EAL: Create bonded device net_bond_0 on port 0 in mode 0 on socket 0. 1778 Port 0 is attached. Now total ports is 1 1779 Done 1780 1781 1782port detach 1783~~~~~~~~~~~ 1784 1785Detach a specific port:: 1786 1787 testpmd> port detach (port_id) 1788 1789Before detaching a port, the port should be stopped and closed. 1790 1791For example, to detach a pci device port 0. 1792 1793.. code-block:: console 1794 1795 testpmd> port stop 0 1796 Stopping ports... 1797 Done 1798 testpmd> port close 0 1799 Closing ports... 1800 Done 1801 1802 testpmd> port detach 0 1803 Detaching a port... 1804 EAL: PCI device 0000:0a:00.0 on NUMA socket -1 1805 EAL: remove driver: 8086:10fb rte_ixgbe_pmd 1806 EAL: PCI memory unmapped at 0x7f83bfa00000 1807 EAL: PCI memory unmapped at 0x7f83bfa80000 1808 Done 1809 1810 1811For example, to detach a virtual device port 0. 1812 1813.. code-block:: console 1814 1815 testpmd> port stop 0 1816 Stopping ports... 1817 Done 1818 testpmd> port close 0 1819 Closing ports... 1820 Done 1821 1822 testpmd> port detach 0 1823 Detaching a port... 1824 PMD: Closing pcap ethdev on numa socket 0 1825 Port 'net_pcap0' is detached. Now total ports is 0 1826 Done 1827 1828To remove a pci device completely from the system, first detach the port from testpmd. 1829Then the device should be moved under kernel management. 1830Finally the device can be removed using kernel pci hotplug functionality. 1831 1832For example, to move a pci device under kernel management: 1833 1834.. code-block:: console 1835 1836 sudo ./usertools/dpdk-devbind.py -b ixgbe 0000:0a:00.0 1837 1838 ./usertools/dpdk-devbind.py --status 1839 1840 Network devices using DPDK-compatible driver 1841 ============================================ 1842 <none> 1843 1844 Network devices using kernel driver 1845 =================================== 1846 0000:0a:00.0 '82599ES 10-Gigabit' if=eth2 drv=ixgbe unused=igb_uio 1847 1848To remove a port created by a virtual device, above steps are not needed. 1849 1850port start 1851~~~~~~~~~~ 1852 1853Start all ports or a specific port:: 1854 1855 testpmd> port start (port_id|all) 1856 1857port stop 1858~~~~~~~~~ 1859 1860Stop all ports or a specific port:: 1861 1862 testpmd> port stop (port_id|all) 1863 1864port close 1865~~~~~~~~~~ 1866 1867Close all ports or a specific port:: 1868 1869 testpmd> port close (port_id|all) 1870 1871port config - queue ring size 1872~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1873 1874Configure a rx/tx queue ring size:: 1875 1876 testpmd> port (port_id) (rxq|txq) (queue_id) ring_size (value) 1877 1878Only take effect after command that (re-)start the port or command that setup specific queue. 1879 1880port start/stop queue 1881~~~~~~~~~~~~~~~~~~~~~ 1882 1883Start/stop a rx/tx queue on a specific port:: 1884 1885 testpmd> port (port_id) (rxq|txq) (queue_id) (start|stop) 1886 1887port config - queue deferred start 1888~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1889 1890Switch on/off deferred start of a specific port queue:: 1891 1892 testpmd> port (port_id) (rxq|txq) (queue_id) deferred_start (on|off) 1893 1894port setup queue 1895~~~~~~~~~~~~~~~~~~~~~ 1896 1897Setup a rx/tx queue on a specific port:: 1898 1899 testpmd> port (port_id) (rxq|txq) (queue_id) setup 1900 1901Only take effect when port is started. 1902 1903port config - speed 1904~~~~~~~~~~~~~~~~~~~ 1905 1906Set the speed and duplex mode for all ports or a specific port:: 1907 1908 testpmd> port config (port_id|all) speed (10|100|1000|10000|25000|40000|50000|100000|auto) \ 1909 duplex (half|full|auto) 1910 1911port config - queues/descriptors 1912~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1913 1914Set number of queues/descriptors for rxq, txq, rxd and txd:: 1915 1916 testpmd> port config all (rxq|txq|rxd|txd) (value) 1917 1918This is equivalent to the ``--rxq``, ``--txq``, ``--rxd`` and ``--txd`` command-line options. 1919 1920port config - max-pkt-len 1921~~~~~~~~~~~~~~~~~~~~~~~~~ 1922 1923Set the maximum packet length:: 1924 1925 testpmd> port config all max-pkt-len (value) 1926 1927This is equivalent to the ``--max-pkt-len`` command-line option. 1928 1929port config - CRC Strip 1930~~~~~~~~~~~~~~~~~~~~~~~ 1931 1932Set hardware CRC stripping on or off for all ports:: 1933 1934 testpmd> port config all crc-strip (on|off) 1935 1936CRC stripping is on by default. 1937 1938The ``off`` option is equivalent to the ``--disable-crc-strip`` command-line option. 1939 1940port config - scatter 1941~~~~~~~~~~~~~~~~~~~~~~~ 1942 1943Set RX scatter mode on or off for all ports:: 1944 1945 testpmd> port config all scatter (on|off) 1946 1947RX scatter mode is off by default. 1948 1949The ``on`` option is equivalent to the ``--enable-scatter`` command-line option. 1950 1951port config - RX Checksum 1952~~~~~~~~~~~~~~~~~~~~~~~~~ 1953 1954Set hardware RX checksum offload to on or off for all ports:: 1955 1956 testpmd> port config all rx-cksum (on|off) 1957 1958Checksum offload is off by default. 1959 1960The ``on`` option is equivalent to the ``--enable-rx-cksum`` command-line option. 1961 1962port config - VLAN 1963~~~~~~~~~~~~~~~~~~ 1964 1965Set hardware VLAN on or off for all ports:: 1966 1967 testpmd> port config all hw-vlan (on|off) 1968 1969Hardware VLAN is off by default. 1970 1971The ``on`` option is equivalent to the ``--enable-hw-vlan`` command-line option. 1972 1973port config - VLAN filter 1974~~~~~~~~~~~~~~~~~~~~~~~~~ 1975 1976Set hardware VLAN filter on or off for all ports:: 1977 1978 testpmd> port config all hw-vlan-filter (on|off) 1979 1980Hardware VLAN filter is off by default. 1981 1982The ``on`` option is equivalent to the ``--enable-hw-vlan-filter`` command-line option. 1983 1984port config - VLAN strip 1985~~~~~~~~~~~~~~~~~~~~~~~~ 1986 1987Set hardware VLAN strip on or off for all ports:: 1988 1989 testpmd> port config all hw-vlan-strip (on|off) 1990 1991Hardware VLAN strip is off by default. 1992 1993The ``on`` option is equivalent to the ``--enable-hw-vlan-strip`` command-line option. 1994 1995port config - VLAN extend 1996~~~~~~~~~~~~~~~~~~~~~~~~~ 1997 1998Set hardware VLAN extend on or off for all ports:: 1999 2000 testpmd> port config all hw-vlan-extend (on|off) 2001 2002Hardware VLAN extend is off by default. 2003 2004The ``on`` option is equivalent to the ``--enable-hw-vlan-extend`` command-line option. 2005 2006port config - Drop Packets 2007~~~~~~~~~~~~~~~~~~~~~~~~~~ 2008 2009Set packet drop for packets with no descriptors on or off for all ports:: 2010 2011 testpmd> port config all drop-en (on|off) 2012 2013Packet dropping for packets with no descriptors is off by default. 2014 2015The ``on`` option is equivalent to the ``--enable-drop-en`` command-line option. 2016 2017port config - RSS 2018~~~~~~~~~~~~~~~~~ 2019 2020Set the RSS (Receive Side Scaling) mode on or off:: 2021 2022 testpmd> port config all rss (all|default|ip|tcp|udp|sctp|ether|port|vxlan|geneve|nvgre|none) 2023 2024RSS is on by default. 2025 2026The ``all`` option is equivalent to ip|tcp|udp|sctp|ether. 2027The ``default`` option enables all supported RSS types reported by device info. 2028The ``none`` option is equivalent to the ``--disable-rss`` command-line option. 2029 2030port config - RSS Reta 2031~~~~~~~~~~~~~~~~~~~~~~ 2032 2033Set the RSS (Receive Side Scaling) redirection table:: 2034 2035 testpmd> port config all rss reta (hash,queue)[,(hash,queue)] 2036 2037port config - DCB 2038~~~~~~~~~~~~~~~~~ 2039 2040Set the DCB mode for an individual port:: 2041 2042 testpmd> port config (port_id) dcb vt (on|off) (traffic_class) pfc (on|off) 2043 2044The traffic class should be 4 or 8. 2045 2046port config - Burst 2047~~~~~~~~~~~~~~~~~~~ 2048 2049Set the number of packets per burst:: 2050 2051 testpmd> port config all burst (value) 2052 2053This is equivalent to the ``--burst`` command-line option. 2054 2055port config - Threshold 2056~~~~~~~~~~~~~~~~~~~~~~~ 2057 2058Set thresholds for TX/RX queues:: 2059 2060 testpmd> port config all (threshold) (value) 2061 2062Where the threshold type can be: 2063 2064* ``txpt:`` Set the prefetch threshold register of the TX rings, 0 <= value <= 255. 2065 2066* ``txht:`` Set the host threshold register of the TX rings, 0 <= value <= 255. 2067 2068* ``txwt:`` Set the write-back threshold register of the TX rings, 0 <= value <= 255. 2069 2070* ``rxpt:`` Set the prefetch threshold register of the RX rings, 0 <= value <= 255. 2071 2072* ``rxht:`` Set the host threshold register of the RX rings, 0 <= value <= 255. 2073 2074* ``rxwt:`` Set the write-back threshold register of the RX rings, 0 <= value <= 255. 2075 2076* ``txfreet:`` Set the transmit free threshold of the TX rings, 0 <= value <= txd. 2077 2078* ``rxfreet:`` Set the transmit free threshold of the RX rings, 0 <= value <= rxd. 2079 2080* ``txrst:`` Set the transmit RS bit threshold of TX rings, 0 <= value <= txd. 2081 2082These threshold options are also available from the command-line. 2083 2084port config - E-tag 2085~~~~~~~~~~~~~~~~~~~ 2086 2087Set the value of ether-type for E-tag:: 2088 2089 testpmd> port config (port_id|all) l2-tunnel E-tag ether-type (value) 2090 2091Enable/disable the E-tag support:: 2092 2093 testpmd> port config (port_id|all) l2-tunnel E-tag (enable|disable) 2094 2095port config pctype mapping 2096~~~~~~~~~~~~~~~~~~~~~~~~~~ 2097 2098Reset pctype mapping table:: 2099 2100 testpmd> port config (port_id) pctype mapping reset 2101 2102Update hardware defined pctype to software defined flow type mapping table:: 2103 2104 testpmd> port config (port_id) pctype mapping update (pctype_id_0[,pctype_id_1]*) (flow_type_id) 2105 2106where: 2107 2108* ``pctype_id_x``: hardware pctype id as index of bit in bitmask value of the pctype mapping table. 2109 2110* ``flow_type_id``: software flow type id as the index of the pctype mapping table. 2111 2112port config input set 2113~~~~~~~~~~~~~~~~~~~~~ 2114 2115Config RSS/FDIR/FDIR flexible payload input set for some pctype:: 2116 testpmd> port config (port_id) pctype (pctype_id) \ 2117 (hash_inset|fdir_inset|fdir_flx_inset) \ 2118 (get|set|clear) field (field_idx) 2119 2120Clear RSS/FDIR/FDIR flexible payload input set for some pctype:: 2121 testpmd> port config (port_id) pctype (pctype_id) \ 2122 (hash_inset|fdir_inset|fdir_flx_inset) clear all 2123 2124where: 2125 2126* ``pctype_id``: hardware packet classification types. 2127* ``field_idx``: hardware field index. 2128 2129port config udp_tunnel_port 2130~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2131 2132Add/remove UDP tunnel port for VXLAN/GENEVE tunneling protocols:: 2133 testpmd> port config (port_id) udp_tunnel_port add|rm vxlan|geneve (udp_port) 2134 2135port config tx_metadata 2136~~~~~~~~~~~~~~~~~~~~~~~ 2137 2138Set Tx metadata value per port. 2139testpmd will add this value to any Tx packet sent from this port:: 2140 2141 testpmd> port config (port_id) tx_metadata (value) 2142 2143Link Bonding Functions 2144---------------------- 2145 2146The Link Bonding functions make it possible to dynamically create and 2147manage link bonding devices from within testpmd interactive prompt. 2148 2149create bonded device 2150~~~~~~~~~~~~~~~~~~~~ 2151 2152Create a new bonding device:: 2153 2154 testpmd> create bonded device (mode) (socket) 2155 2156For example, to create a bonded device in mode 1 on socket 0:: 2157 2158 testpmd> create bonded device 1 0 2159 created new bonded device (port X) 2160 2161add bonding slave 2162~~~~~~~~~~~~~~~~~ 2163 2164Adds Ethernet device to a Link Bonding device:: 2165 2166 testpmd> add bonding slave (slave id) (port id) 2167 2168For example, to add Ethernet device (port 6) to a Link Bonding device (port 10):: 2169 2170 testpmd> add bonding slave 6 10 2171 2172 2173remove bonding slave 2174~~~~~~~~~~~~~~~~~~~~ 2175 2176Removes an Ethernet slave device from a Link Bonding device:: 2177 2178 testpmd> remove bonding slave (slave id) (port id) 2179 2180For example, to remove Ethernet slave device (port 6) to a Link Bonding device (port 10):: 2181 2182 testpmd> remove bonding slave 6 10 2183 2184set bonding mode 2185~~~~~~~~~~~~~~~~ 2186 2187Set the Link Bonding mode of a Link Bonding device:: 2188 2189 testpmd> set bonding mode (value) (port id) 2190 2191For example, to set the bonding mode of a Link Bonding device (port 10) to broadcast (mode 3):: 2192 2193 testpmd> set bonding mode 3 10 2194 2195set bonding primary 2196~~~~~~~~~~~~~~~~~~~ 2197 2198Set an Ethernet slave device as the primary device on a Link Bonding device:: 2199 2200 testpmd> set bonding primary (slave id) (port id) 2201 2202For example, to set the Ethernet slave device (port 6) as the primary port of a Link Bonding device (port 10):: 2203 2204 testpmd> set bonding primary 6 10 2205 2206set bonding mac 2207~~~~~~~~~~~~~~~ 2208 2209Set the MAC address of a Link Bonding device:: 2210 2211 testpmd> set bonding mac (port id) (mac) 2212 2213For example, to set the MAC address of a Link Bonding device (port 10) to 00:00:00:00:00:01:: 2214 2215 testpmd> set bonding mac 10 00:00:00:00:00:01 2216 2217set bonding xmit_balance_policy 2218~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2219 2220Set the transmission policy for a Link Bonding device when it is in Balance XOR mode:: 2221 2222 testpmd> set bonding xmit_balance_policy (port_id) (l2|l23|l34) 2223 2224For example, set a Link Bonding device (port 10) to use a balance policy of layer 3+4 (IP addresses & UDP ports):: 2225 2226 testpmd> set bonding xmit_balance_policy 10 l34 2227 2228 2229set bonding mon_period 2230~~~~~~~~~~~~~~~~~~~~~~ 2231 2232Set the link status monitoring polling period in milliseconds for a bonding device. 2233 2234This adds support for PMD slave devices which do not support link status interrupts. 2235When the mon_period is set to a value greater than 0 then all PMD's which do not support 2236link status ISR will be queried every polling interval to check if their link status has changed:: 2237 2238 testpmd> set bonding mon_period (port_id) (value) 2239 2240For example, to set the link status monitoring polling period of bonded device (port 5) to 150ms:: 2241 2242 testpmd> set bonding mon_period 5 150 2243 2244 2245set bonding lacp dedicated_queue 2246~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2247 2248Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic 2249when in mode 4 (link-aggregration-802.3ad):: 2250 2251 testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable) 2252 2253 2254set bonding agg_mode 2255~~~~~~~~~~~~~~~~~~~~ 2256 2257Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad):: 2258 2259 testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable) 2260 2261 2262show bonding config 2263~~~~~~~~~~~~~~~~~~~ 2264 2265Show the current configuration of a Link Bonding device:: 2266 2267 testpmd> show bonding config (port id) 2268 2269For example, 2270to show the configuration a Link Bonding device (port 9) with 3 slave devices (1, 3, 4) 2271in balance mode with a transmission policy of layer 2+3:: 2272 2273 testpmd> show bonding config 9 2274 Bonding mode: 2 2275 Balance Xmit Policy: BALANCE_XMIT_POLICY_LAYER23 2276 Slaves (3): [1 3 4] 2277 Active Slaves (3): [1 3 4] 2278 Primary: [3] 2279 2280 2281Register Functions 2282------------------ 2283 2284The Register Functions can be used to read from and write to registers on the network card referenced by a port number. 2285This is mainly useful for debugging purposes. 2286Reference should be made to the appropriate datasheet for the network card for details on the register addresses 2287and fields that can be accessed. 2288 2289read reg 2290~~~~~~~~ 2291 2292Display the value of a port register:: 2293 2294 testpmd> read reg (port_id) (address) 2295 2296For example, to examine the Flow Director control register (FDIRCTL, 0x0000EE000) on an Intel 82599 10 GbE Controller:: 2297 2298 testpmd> read reg 0 0xEE00 2299 port 0 PCI register at offset 0xEE00: 0x4A060029 (1241907241) 2300 2301read regfield 2302~~~~~~~~~~~~~ 2303 2304Display a port register bit field:: 2305 2306 testpmd> read regfield (port_id) (address) (bit_x) (bit_y) 2307 2308For example, reading the lowest two bits from the register in the example above:: 2309 2310 testpmd> read regfield 0 0xEE00 0 1 2311 port 0 PCI register at offset 0xEE00: bits[0, 1]=0x1 (1) 2312 2313read regbit 2314~~~~~~~~~~~ 2315 2316Display a single port register bit:: 2317 2318 testpmd> read regbit (port_id) (address) (bit_x) 2319 2320For example, reading the lowest bit from the register in the example above:: 2321 2322 testpmd> read regbit 0 0xEE00 0 2323 port 0 PCI register at offset 0xEE00: bit 0=1 2324 2325write reg 2326~~~~~~~~~ 2327 2328Set the value of a port register:: 2329 2330 testpmd> write reg (port_id) (address) (value) 2331 2332For example, to clear a register:: 2333 2334 testpmd> write reg 0 0xEE00 0x0 2335 port 0 PCI register at offset 0xEE00: 0x00000000 (0) 2336 2337write regfield 2338~~~~~~~~~~~~~~ 2339 2340Set bit field of a port register:: 2341 2342 testpmd> write regfield (port_id) (address) (bit_x) (bit_y) (value) 2343 2344For example, writing to the register cleared in the example above:: 2345 2346 testpmd> write regfield 0 0xEE00 0 1 2 2347 port 0 PCI register at offset 0xEE00: 0x00000002 (2) 2348 2349write regbit 2350~~~~~~~~~~~~ 2351 2352Set single bit value of a port register:: 2353 2354 testpmd> write regbit (port_id) (address) (bit_x) (value) 2355 2356For example, to set the high bit in the register from the example above:: 2357 2358 testpmd> write regbit 0 0xEE00 31 1 2359 port 0 PCI register at offset 0xEE00: 0x8000000A (2147483658) 2360 2361Traffic Metering and Policing 2362----------------------------- 2363 2364The following section shows functions for configuring traffic metering and 2365policing on the ethernet device through the use of generic ethdev API. 2366 2367show port traffic management capability 2368~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2369 2370Show traffic metering and policing capability of the port:: 2371 2372 testpmd> show port meter cap (port_id) 2373 2374add port meter profile (srTCM rfc2967) 2375~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2376 2377Add meter profile (srTCM rfc2697) to the ethernet device:: 2378 2379 testpmd> add port meter profile srtcm_rfc2697 (port_id) (profile_id) \ 2380 (cir) (cbs) (ebs) 2381 2382where: 2383 2384* ``profile_id``: ID for the meter profile. 2385* ``cir``: Committed Information Rate (CIR) (bytes/second). 2386* ``cbs``: Committed Burst Size (CBS) (bytes). 2387* ``ebs``: Excess Burst Size (EBS) (bytes). 2388 2389add port meter profile (trTCM rfc2968) 2390~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2391 2392Add meter profile (srTCM rfc2698) to the ethernet device:: 2393 2394 testpmd> add port meter profile trtcm_rfc2698 (port_id) (profile_id) \ 2395 (cir) (pir) (cbs) (pbs) 2396 2397where: 2398 2399* ``profile_id``: ID for the meter profile. 2400* ``cir``: Committed information rate (bytes/second). 2401* ``pir``: Peak information rate (bytes/second). 2402* ``cbs``: Committed burst size (bytes). 2403* ``pbs``: Peak burst size (bytes). 2404 2405add port meter profile (trTCM rfc4115) 2406~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2407 2408Add meter profile (trTCM rfc4115) to the ethernet device:: 2409 2410 testpmd> add port meter profile trtcm_rfc4115 (port_id) (profile_id) \ 2411 (cir) (eir) (cbs) (ebs) 2412 2413where: 2414 2415* ``profile_id``: ID for the meter profile. 2416* ``cir``: Committed information rate (bytes/second). 2417* ``eir``: Excess information rate (bytes/second). 2418* ``cbs``: Committed burst size (bytes). 2419* ``ebs``: Excess burst size (bytes). 2420 2421delete port meter profile 2422~~~~~~~~~~~~~~~~~~~~~~~~~ 2423 2424Delete meter profile from the ethernet device:: 2425 2426 testpmd> del port meter profile (port_id) (profile_id) 2427 2428create port meter 2429~~~~~~~~~~~~~~~~~ 2430 2431Create new meter object for the ethernet device:: 2432 2433 testpmd> create port meter (port_id) (mtr_id) (profile_id) \ 2434 (meter_enable) (g_action) (y_action) (r_action) (stats_mask) (shared) \ 2435 (use_pre_meter_color) [(dscp_tbl_entry0) (dscp_tbl_entry1)...\ 2436 (dscp_tbl_entry63)] 2437 2438where: 2439 2440* ``mtr_id``: meter object ID. 2441* ``profile_id``: ID for the meter profile. 2442* ``meter_enable``: When this parameter has a non-zero value, the meter object 2443 gets enabled at the time of creation, otherwise remains disabled. 2444* ``g_action``: Policer action for the packet with green color. 2445* ``y_action``: Policer action for the packet with yellow color. 2446* ``r_action``: Policer action for the packet with red color. 2447* ``stats_mask``: Mask of statistics counter types to be enabled for the 2448 meter object. 2449* ``shared``: When this parameter has a non-zero value, the meter object is 2450 shared by multiple flows. Otherwise, meter object is used by single flow. 2451* ``use_pre_meter_color``: When this parameter has a non-zero value, the 2452 input color for the current meter object is determined by the latest meter 2453 object in the same flow. Otherwise, the current meter object uses the 2454 *dscp_table* to determine the input color. 2455* ``dscp_tbl_entryx``: DSCP table entry x providing meter providing input 2456 color, 0 <= x <= 63. 2457 2458enable port meter 2459~~~~~~~~~~~~~~~~~ 2460 2461Enable meter for the ethernet device:: 2462 2463 testpmd> enable port meter (port_id) (mtr_id) 2464 2465disable port meter 2466~~~~~~~~~~~~~~~~~~ 2467 2468Disable meter for the ethernet device:: 2469 2470 testpmd> disable port meter (port_id) (mtr_id) 2471 2472delete port meter 2473~~~~~~~~~~~~~~~~~ 2474 2475Delete meter for the ethernet device:: 2476 2477 testpmd> del port meter (port_id) (mtr_id) 2478 2479Set port meter profile 2480~~~~~~~~~~~~~~~~~~~~~~ 2481 2482Set meter profile for the ethernet device:: 2483 2484 testpmd> set port meter profile (port_id) (mtr_id) (profile_id) 2485 2486set port meter dscp table 2487~~~~~~~~~~~~~~~~~~~~~~~~~ 2488 2489Set meter dscp table for the ethernet device:: 2490 2491 testpmd> set port meter dscp table (port_id) (mtr_id) [(dscp_tbl_entry0) \ 2492 (dscp_tbl_entry1)...(dscp_tbl_entry63)] 2493 2494set port meter policer action 2495~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2496 2497Set meter policer action for the ethernet device:: 2498 2499 testpmd> set port meter policer action (port_id) (mtr_id) (action_mask) \ 2500 (action0) [(action1) (action1)] 2501 2502where: 2503 2504* ``action_mask``: Bit mask indicating which policer actions need to be 2505 updated. One or more policer actions can be updated in a single function 2506 invocation. To update the policer action associated with color C, bit 2507 (1 << C) needs to be set in *action_mask* and element at position C 2508 in the *actions* array needs to be valid. 2509* ``actionx``: Policer action for the color x, 2510 RTE_MTR_GREEN <= x < RTE_MTR_COLORS 2511 2512set port meter stats mask 2513~~~~~~~~~~~~~~~~~~~~~~~~~ 2514 2515Set meter stats mask for the ethernet device:: 2516 2517 testpmd> set port meter stats mask (port_id) (mtr_id) (stats_mask) 2518 2519where: 2520 2521* ``stats_mask``: Bit mask indicating statistics counter types to be enabled. 2522 2523show port meter stats 2524~~~~~~~~~~~~~~~~~~~~~ 2525 2526Show meter stats of the ethernet device:: 2527 2528 testpmd> show port meter stats (port_id) (mtr_id) (clear) 2529 2530where: 2531 2532* ``clear``: Flag that indicates whether the statistics counters should 2533 be cleared (i.e. set to zero) immediately after they have been read or not. 2534 2535Traffic Management 2536------------------ 2537 2538The following section shows functions for configuring traffic management on 2539on the ethernet device through the use of generic TM API. 2540 2541show port traffic management capability 2542~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2543 2544Show traffic management capability of the port:: 2545 2546 testpmd> show port tm cap (port_id) 2547 2548show port traffic management capability (hierarchy level) 2549~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2550 2551Show traffic management hierarchy level capability of the port:: 2552 2553 testpmd> show port tm level cap (port_id) (level_id) 2554 2555show port traffic management capability (hierarchy node level) 2556~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2557 2558Show the traffic management hierarchy node capability of the port:: 2559 2560 testpmd> show port tm node cap (port_id) (node_id) 2561 2562show port traffic management hierarchy node type 2563~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2564 2565Show the port traffic management hierarchy node type:: 2566 2567 testpmd> show port tm node type (port_id) (node_id) 2568 2569show port traffic management hierarchy node stats 2570~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2571 2572Show the port traffic management hierarchy node statistics:: 2573 2574 testpmd> show port tm node stats (port_id) (node_id) (clear) 2575 2576where: 2577 2578* ``clear``: When this parameter has a non-zero value, the statistics counters 2579 are cleared (i.e. set to zero) immediately after they have been read, 2580 otherwise the statistics counters are left untouched. 2581 2582Add port traffic management private shaper profile 2583~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2584 2585Add the port traffic management private shaper profile:: 2586 2587 testpmd> add port tm node shaper profile (port_id) (shaper_profile_id) \ 2588 (cmit_tb_rate) (cmit_tb_size) (peak_tb_rate) (peak_tb_size) \ 2589 (packet_length_adjust) 2590 2591where: 2592 2593* ``shaper_profile id``: Shaper profile ID for the new profile. 2594* ``cmit_tb_rate``: Committed token bucket rate (bytes per second). 2595* ``cmit_tb_size``: Committed token bucket size (bytes). 2596* ``peak_tb_rate``: Peak token bucket rate (bytes per second). 2597* ``peak_tb_size``: Peak token bucket size (bytes). 2598* ``packet_length_adjust``: The value (bytes) to be added to the length of 2599 each packet for the purpose of shaping. This parameter value can be used to 2600 correct the packet length with the framing overhead bytes that are consumed 2601 on the wire. 2602 2603Delete port traffic management private shaper profile 2604~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2605 2606Delete the port traffic management private shaper:: 2607 2608 testpmd> del port tm node shaper profile (port_id) (shaper_profile_id) 2609 2610where: 2611 2612* ``shaper_profile id``: Shaper profile ID that needs to be deleted. 2613 2614Add port traffic management shared shaper 2615~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2616 2617Create the port traffic management shared shaper:: 2618 2619 testpmd> add port tm node shared shaper (port_id) (shared_shaper_id) \ 2620 (shaper_profile_id) 2621 2622where: 2623 2624* ``shared_shaper_id``: Shared shaper ID to be created. 2625* ``shaper_profile id``: Shaper profile ID for shared shaper. 2626 2627Set port traffic management shared shaper 2628~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2629 2630Update the port traffic management shared shaper:: 2631 2632 testpmd> set port tm node shared shaper (port_id) (shared_shaper_id) \ 2633 (shaper_profile_id) 2634 2635where: 2636 2637* ``shared_shaper_id``: Shared shaper ID to be update. 2638* ``shaper_profile id``: Shaper profile ID for shared shaper. 2639 2640Delete port traffic management shared shaper 2641~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2642 2643Delete the port traffic management shared shaper:: 2644 2645 testpmd> del port tm node shared shaper (port_id) (shared_shaper_id) 2646 2647where: 2648 2649* ``shared_shaper_id``: Shared shaper ID to be deleted. 2650 2651Set port traffic management hiearchy node private shaper 2652~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2653 2654set the port traffic management hierarchy node private shaper:: 2655 2656 testpmd> set port tm node shaper profile (port_id) (node_id) \ 2657 (shaper_profile_id) 2658 2659where: 2660 2661* ``shaper_profile id``: Private shaper profile ID to be enabled on the 2662 hierarchy node. 2663 2664Add port traffic management WRED profile 2665~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2666 2667Create a new WRED profile:: 2668 2669 testpmd> add port tm node wred profile (port_id) (wred_profile_id) \ 2670 (color_g) (min_th_g) (max_th_g) (maxp_inv_g) (wq_log2_g) \ 2671 (color_y) (min_th_y) (max_th_y) (maxp_inv_y) (wq_log2_y) \ 2672 (color_r) (min_th_r) (max_th_r) (maxp_inv_r) (wq_log2_r) 2673 2674where: 2675 2676* ``wred_profile id``: Identifier for the newly create WRED profile 2677* ``color_g``: Packet color (green) 2678* ``min_th_g``: Minimum queue threshold for packet with green color 2679* ``max_th_g``: Minimum queue threshold for packet with green color 2680* ``maxp_inv_g``: Inverse of packet marking probability maximum value (maxp) 2681* ``wq_log2_g``: Negated log2 of queue weight (wq) 2682* ``color_y``: Packet color (yellow) 2683* ``min_th_y``: Minimum queue threshold for packet with yellow color 2684* ``max_th_y``: Minimum queue threshold for packet with yellow color 2685* ``maxp_inv_y``: Inverse of packet marking probability maximum value (maxp) 2686* ``wq_log2_y``: Negated log2 of queue weight (wq) 2687* ``color_r``: Packet color (red) 2688* ``min_th_r``: Minimum queue threshold for packet with yellow color 2689* ``max_th_r``: Minimum queue threshold for packet with yellow color 2690* ``maxp_inv_r``: Inverse of packet marking probability maximum value (maxp) 2691* ``wq_log2_r``: Negated log2 of queue weight (wq) 2692 2693Delete port traffic management WRED profile 2694~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2695 2696Delete the WRED profile:: 2697 2698 testpmd> del port tm node wred profile (port_id) (wred_profile_id) 2699 2700Add port traffic management hierarchy nonleaf node 2701~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2702 2703Add nonleaf node to port traffic management hiearchy:: 2704 2705 testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \ 2706 (priority) (weight) (level_id) (shaper_profile_id) \ 2707 (n_sp_priorities) (stats_mask) (n_shared_shapers) \ 2708 [(shared_shaper_0) (shared_shaper_1) ...] \ 2709 2710where: 2711 2712* ``parent_node_id``: Node ID of the parent. 2713* ``priority``: Node priority (highest node priority is zero). This is used by 2714 the SP algorithm running on the parent node for scheduling this node. 2715* ``weight``: Node weight (lowest weight is one). The node weight is relative 2716 to the weight sum of all siblings that have the same priority. It is used by 2717 the WFQ algorithm running on the parent node for scheduling this node. 2718* ``level_id``: Hiearchy level of the node. 2719* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by 2720 the node. 2721* ``n_sp_priorities``: Number of strict priorities. 2722* ``stats_mask``: Mask of statistics counter types to be enabled for this node. 2723* ``n_shared_shapers``: Number of shared shapers. 2724* ``shared_shaper_id``: Shared shaper id. 2725 2726Add port traffic management hierarchy leaf node 2727~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2728 2729Add leaf node to port traffic management hiearchy:: 2730 2731 testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \ 2732 (priority) (weight) (level_id) (shaper_profile_id) \ 2733 (cman_mode) (wred_profile_id) (stats_mask) (n_shared_shapers) \ 2734 [(shared_shaper_id) (shared_shaper_id) ...] \ 2735 2736where: 2737 2738* ``parent_node_id``: Node ID of the parent. 2739* ``priority``: Node priority (highest node priority is zero). This is used by 2740 the SP algorithm running on the parent node for scheduling this node. 2741* ``weight``: Node weight (lowest weight is one). The node weight is relative 2742 to the weight sum of all siblings that have the same priority. It is used by 2743 the WFQ algorithm running on the parent node for scheduling this node. 2744* ``level_id``: Hiearchy level of the node. 2745* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by 2746 the node. 2747* ``cman_mode``: Congestion management mode to be enabled for this node. 2748* ``wred_profile_id``: WRED profile id to be enabled for this node. 2749* ``stats_mask``: Mask of statistics counter types to be enabled for this node. 2750* ``n_shared_shapers``: Number of shared shapers. 2751* ``shared_shaper_id``: Shared shaper id. 2752 2753Delete port traffic management hierarchy node 2754~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2755 2756Delete node from port traffic management hiearchy:: 2757 2758 testpmd> del port tm node (port_id) (node_id) 2759 2760Update port traffic management hierarchy parent node 2761~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2762 2763Update port traffic management hierarchy parent node:: 2764 2765 testpmd> set port tm node parent (port_id) (node_id) (parent_node_id) \ 2766 (priority) (weight) 2767 2768This function can only be called after the hierarchy commit invocation. Its 2769success depends on the port support for this operation, as advertised through 2770the port capability set. This function is valid for all nodes of the traffic 2771management hierarchy except root node. 2772 2773Suspend port traffic management hierarchy node 2774~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2775 2776 testpmd> suspend port tm node (port_id) (node_id) 2777 2778Resume port traffic management hierarchy node 2779~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2780 2781 testpmd> resume port tm node (port_id) (node_id) 2782 2783Commit port traffic management hierarchy 2784~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2785 2786Commit the traffic management hierarchy on the port:: 2787 2788 testpmd> port tm hierarchy commit (port_id) (clean_on_fail) 2789 2790where: 2791 2792* ``clean_on_fail``: When set to non-zero, hierarchy is cleared on function 2793 call failure. On the other hand, hierarchy is preserved when this parameter 2794 is equal to zero. 2795 2796Set port traffic management mark VLAN dei 2797~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2798 2799Enables/Disables the traffic management marking on the port for VLAN packets:: 2800 2801 testpmd> set port tm mark vlan_dei <port_id> <green> <yellow> <red> 2802 2803where: 2804 2805* ``port_id``: The port which on which VLAN packets marked as ``green`` or 2806 ``yellow`` or ``red`` will have dei bit enabled 2807 2808* ``green`` enable 1, disable 0 marking for dei bit of VLAN packets marked as green 2809 2810* ``yellow`` enable 1, disable 0 marking for dei bit of VLAN packets marked as yellow 2811 2812* ``red`` enable 1, disable 0 marking for dei bit of VLAN packets marked as red 2813 2814Set port traffic management mark IP dscp 2815~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2816 2817Enables/Disables the traffic management marking on the port for IP dscp packets:: 2818 2819 testpmd> set port tm mark ip_dscp <port_id> <green> <yellow> <red> 2820 2821where: 2822 2823* ``port_id``: The port which on which IP packets marked as ``green`` or 2824 ``yellow`` or ``red`` will have IP dscp bits updated 2825 2826* ``green`` enable 1, disable 0 marking IP dscp to low drop precedence for green packets 2827 2828* ``yellow`` enable 1, disable 0 marking IP dscp to medium drop precedence for yellow packets 2829 2830* ``red`` enable 1, disable 0 marking IP dscp to high drop precedence for red packets 2831 2832Set port traffic management mark IP ecn 2833~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2834 2835Enables/Disables the traffic management marking on the port for IP ecn packets:: 2836 2837 testpmd> set port tm mark ip_ecn <port_id> <green> <yellow> <red> 2838 2839where: 2840 2841* ``port_id``: The port which on which IP packets marked as ``green`` or 2842 ``yellow`` or ``red`` will have IP ecn bits updated 2843 2844* ``green`` enable 1, disable 0 marking IP ecn for green marked packets with ecn of 2'b01 or 2'b10 2845 to ecn of 2'b11 when IP is caring TCP or SCTP 2846 2847* ``yellow`` enable 1, disable 0 marking IP ecn for yellow marked packets with ecn of 2'b01 or 2'b10 2848 to ecn of 2'b11 when IP is caring TCP or SCTP 2849 2850* ``red`` enable 1, disable 0 marking IP ecn for yellow marked packets with ecn of 2'b01 or 2'b10 2851 to ecn of 2'b11 when IP is caring TCP or SCTP 2852 2853Set port traffic management default hierarchy (softnic forwarding mode) 2854~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2855 2856set the traffic management default hierarchy on the port:: 2857 2858 testpmd> set port tm hierarchy default (port_id) 2859 2860Filter Functions 2861---------------- 2862 2863This section details the available filter functions that are available. 2864 2865Note these functions interface the deprecated legacy filtering framework, 2866superseded by *rte_flow*. See `Flow rules management`_. 2867 2868ethertype_filter 2869~~~~~~~~~~~~~~~~~~~~ 2870 2871Add or delete a L2 Ethertype filter, which identify packets by their L2 Ethertype mainly assign them to a receive queue:: 2872 2873 ethertype_filter (port_id) (add|del) (mac_addr|mac_ignr) (mac_address) \ 2874 ethertype (ether_type) (drop|fwd) queue (queue_id) 2875 2876The available information parameters are: 2877 2878* ``port_id``: The port which the Ethertype filter assigned on. 2879 2880* ``mac_addr``: Compare destination mac address. 2881 2882* ``mac_ignr``: Ignore destination mac address match. 2883 2884* ``mac_address``: Destination mac address to match. 2885 2886* ``ether_type``: The EtherType value want to match, 2887 for example 0x0806 for ARP packet. 0x0800 (IPv4) and 0x86DD (IPv6) are invalid. 2888 2889* ``queue_id``: The receive queue associated with this EtherType filter. 2890 It is meaningless when deleting or dropping. 2891 2892Example, to add/remove an ethertype filter rule:: 2893 2894 testpmd> ethertype_filter 0 add mac_ignr 00:11:22:33:44:55 \ 2895 ethertype 0x0806 fwd queue 3 2896 2897 testpmd> ethertype_filter 0 del mac_ignr 00:11:22:33:44:55 \ 2898 ethertype 0x0806 fwd queue 3 2899 29002tuple_filter 2901~~~~~~~~~~~~~~~~~ 2902 2903Add or delete a 2-tuple filter, 2904which identifies packets by specific protocol and destination TCP/UDP port 2905and forwards packets into one of the receive queues:: 2906 2907 2tuple_filter (port_id) (add|del) dst_port (dst_port_value) \ 2908 protocol (protocol_value) mask (mask_value) \ 2909 tcp_flags (tcp_flags_value) priority (prio_value) \ 2910 queue (queue_id) 2911 2912The available information parameters are: 2913 2914* ``port_id``: The port which the 2-tuple filter assigned on. 2915 2916* ``dst_port_value``: Destination port in L4. 2917 2918* ``protocol_value``: IP L4 protocol. 2919 2920* ``mask_value``: Participates in the match or not by bit for field above, 1b means participate. 2921 2922* ``tcp_flags_value``: TCP control bits. The non-zero value is invalid, when the pro_value is not set to 0x06 (TCP). 2923 2924* ``prio_value``: Priority of this filter. 2925 2926* ``queue_id``: The receive queue associated with this 2-tuple filter. 2927 2928Example, to add/remove an 2tuple filter rule:: 2929 2930 testpmd> 2tuple_filter 0 add dst_port 32 protocol 0x06 mask 0x03 \ 2931 tcp_flags 0x02 priority 3 queue 3 2932 2933 testpmd> 2tuple_filter 0 del dst_port 32 protocol 0x06 mask 0x03 \ 2934 tcp_flags 0x02 priority 3 queue 3 2935 29365tuple_filter 2937~~~~~~~~~~~~~~~~~ 2938 2939Add or delete a 5-tuple filter, 2940which consists of a 5-tuple (protocol, source and destination IP addresses, source and destination TCP/UDP/SCTP port) 2941and routes packets into one of the receive queues:: 2942 2943 5tuple_filter (port_id) (add|del) dst_ip (dst_address) src_ip \ 2944 (src_address) dst_port (dst_port_value) \ 2945 src_port (src_port_value) protocol (protocol_value) \ 2946 mask (mask_value) tcp_flags (tcp_flags_value) \ 2947 priority (prio_value) queue (queue_id) 2948 2949The available information parameters are: 2950 2951* ``port_id``: The port which the 5-tuple filter assigned on. 2952 2953* ``dst_address``: Destination IP address. 2954 2955* ``src_address``: Source IP address. 2956 2957* ``dst_port_value``: TCP/UDP destination port. 2958 2959* ``src_port_value``: TCP/UDP source port. 2960 2961* ``protocol_value``: L4 protocol. 2962 2963* ``mask_value``: Participates in the match or not by bit for field above, 1b means participate 2964 2965* ``tcp_flags_value``: TCP control bits. The non-zero value is invalid, when the protocol_value is not set to 0x06 (TCP). 2966 2967* ``prio_value``: The priority of this filter. 2968 2969* ``queue_id``: The receive queue associated with this 5-tuple filter. 2970 2971Example, to add/remove an 5tuple filter rule:: 2972 2973 testpmd> 5tuple_filter 0 add dst_ip 2.2.2.5 src_ip 2.2.2.4 \ 2974 dst_port 64 src_port 32 protocol 0x06 mask 0x1F \ 2975 flags 0x0 priority 3 queue 3 2976 2977 testpmd> 5tuple_filter 0 del dst_ip 2.2.2.5 src_ip 2.2.2.4 \ 2978 dst_port 64 src_port 32 protocol 0x06 mask 0x1F \ 2979 flags 0x0 priority 3 queue 3 2980 2981syn_filter 2982~~~~~~~~~~ 2983 2984Using the SYN filter, TCP packets whose *SYN* flag is set can be forwarded to a separate queue:: 2985 2986 syn_filter (port_id) (add|del) priority (high|low) queue (queue_id) 2987 2988The available information parameters are: 2989 2990* ``port_id``: The port which the SYN filter assigned on. 2991 2992* ``high``: This SYN filter has higher priority than other filters. 2993 2994* ``low``: This SYN filter has lower priority than other filters. 2995 2996* ``queue_id``: The receive queue associated with this SYN filter 2997 2998Example:: 2999 3000 testpmd> syn_filter 0 add priority high queue 3 3001 3002flex_filter 3003~~~~~~~~~~~ 3004 3005With flex filter, packets can be recognized by any arbitrary pattern within the first 128 bytes of the packet 3006and routed into one of the receive queues:: 3007 3008 flex_filter (port_id) (add|del) len (len_value) bytes (bytes_value) \ 3009 mask (mask_value) priority (prio_value) queue (queue_id) 3010 3011The available information parameters are: 3012 3013* ``port_id``: The port which the Flex filter is assigned on. 3014 3015* ``len_value``: Filter length in bytes, no greater than 128. 3016 3017* ``bytes_value``: A string in hexadecimal, means the value the flex filter needs to match. 3018 3019* ``mask_value``: A string in hexadecimal, bit 1 means corresponding byte participates in the match. 3020 3021* ``prio_value``: The priority of this filter. 3022 3023* ``queue_id``: The receive queue associated with this Flex filter. 3024 3025Example:: 3026 3027 testpmd> flex_filter 0 add len 16 bytes 0x00000000000000000000000008060000 \ 3028 mask 000C priority 3 queue 3 3029 3030 testpmd> flex_filter 0 del len 16 bytes 0x00000000000000000000000008060000 \ 3031 mask 000C priority 3 queue 3 3032 3033 3034.. _testpmd_flow_director: 3035 3036flow_director_filter 3037~~~~~~~~~~~~~~~~~~~~ 3038 3039The Flow Director works in receive mode to identify specific flows or sets of flows and route them to specific queues. 3040 3041Four types of filtering are supported which are referred to as Perfect Match, Signature, Perfect-mac-vlan and 3042Perfect-tunnel filters, the match mode is set by the ``--pkt-filter-mode`` command-line parameter: 3043 3044* Perfect match filters. 3045 The hardware checks a match between the masked fields of the received packets and the programmed filters. 3046 The masked fields are for IP flow. 3047 3048* Signature filters. 3049 The hardware checks a match between a hash-based signature of the masked fields of the received packet. 3050 3051* Perfect-mac-vlan match filters. 3052 The hardware checks a match between the masked fields of the received packets and the programmed filters. 3053 The masked fields are for MAC VLAN flow. 3054 3055* Perfect-tunnel match filters. 3056 The hardware checks a match between the masked fields of the received packets and the programmed filters. 3057 The masked fields are for tunnel flow. 3058 3059* Perfect-raw-flow-type match filters. 3060 The hardware checks a match between the masked fields of the received packets and pre-loaded raw (template) packet. 3061 The masked fields are specified by input sets. 3062 3063The Flow Director filters can match the different fields for different type of packet: flow type, specific input set 3064per flow type and the flexible payload. 3065 3066The Flow Director can also mask out parts of all of these fields so that filters 3067are only applied to certain fields or parts of the fields. 3068 3069Note that for raw flow type mode the source and destination fields in the 3070raw packet buffer need to be presented in a reversed order with respect 3071to the expected received packets. 3072For example: IP source and destination addresses or TCP/UDP/SCTP 3073source and destination ports 3074 3075Different NICs may have different capabilities, command show port fdir (port_id) can be used to acquire the information. 3076 3077# Commands to add flow director filters of different flow types:: 3078 3079 flow_director_filter (port_id) mode IP (add|del|update) \ 3080 flow (ipv4-other|ipv4-frag|ipv6-other|ipv6-frag) \ 3081 src (src_ip_address) dst (dst_ip_address) \ 3082 tos (tos_value) proto (proto_value) ttl (ttl_value) \ 3083 vlan (vlan_value) flexbytes (flexbytes_value) \ 3084 (drop|fwd) pf|vf(vf_id) queue (queue_id) \ 3085 fd_id (fd_id_value) 3086 3087 flow_director_filter (port_id) mode IP (add|del|update) \ 3088 flow (ipv4-tcp|ipv4-udp|ipv6-tcp|ipv6-udp) \ 3089 src (src_ip_address) (src_port) \ 3090 dst (dst_ip_address) (dst_port) \ 3091 tos (tos_value) ttl (ttl_value) \ 3092 vlan (vlan_value) flexbytes (flexbytes_value) \ 3093 (drop|fwd) queue pf|vf(vf_id) (queue_id) \ 3094 fd_id (fd_id_value) 3095 3096 flow_director_filter (port_id) mode IP (add|del|update) \ 3097 flow (ipv4-sctp|ipv6-sctp) \ 3098 src (src_ip_address) (src_port) \ 3099 dst (dst_ip_address) (dst_port) \ 3100 tos (tos_value) ttl (ttl_value) \ 3101 tag (verification_tag) vlan (vlan_value) \ 3102 flexbytes (flexbytes_value) (drop|fwd) \ 3103 pf|vf(vf_id) queue (queue_id) fd_id (fd_id_value) 3104 3105 flow_director_filter (port_id) mode IP (add|del|update) flow l2_payload \ 3106 ether (ethertype) flexbytes (flexbytes_value) \ 3107 (drop|fwd) pf|vf(vf_id) queue (queue_id) 3108 fd_id (fd_id_value) 3109 3110 flow_director_filter (port_id) mode MAC-VLAN (add|del|update) \ 3111 mac (mac_address) vlan (vlan_value) \ 3112 flexbytes (flexbytes_value) (drop|fwd) \ 3113 queue (queue_id) fd_id (fd_id_value) 3114 3115 flow_director_filter (port_id) mode Tunnel (add|del|update) \ 3116 mac (mac_address) vlan (vlan_value) \ 3117 tunnel (NVGRE|VxLAN) tunnel-id (tunnel_id_value) \ 3118 flexbytes (flexbytes_value) (drop|fwd) \ 3119 queue (queue_id) fd_id (fd_id_value) 3120 3121 flow_director_filter (port_id) mode raw (add|del|update) flow (flow_id) \ 3122 (drop|fwd) queue (queue_id) fd_id (fd_id_value) \ 3123 packet (packet file name) 3124 3125For example, to add an ipv4-udp flow type filter:: 3126 3127 testpmd> flow_director_filter 0 mode IP add flow ipv4-udp src 2.2.2.3 32 \ 3128 dst 2.2.2.5 33 tos 2 ttl 40 vlan 0x1 flexbytes (0x88,0x48) \ 3129 fwd pf queue 1 fd_id 1 3130 3131For example, add an ipv4-other flow type filter:: 3132 3133 testpmd> flow_director_filter 0 mode IP add flow ipv4-other src 2.2.2.3 \ 3134 dst 2.2.2.5 tos 2 proto 20 ttl 40 vlan 0x1 \ 3135 flexbytes (0x88,0x48) fwd pf queue 1 fd_id 1 3136 3137flush_flow_director 3138~~~~~~~~~~~~~~~~~~~ 3139 3140Flush all flow director filters on a device:: 3141 3142 testpmd> flush_flow_director (port_id) 3143 3144Example, to flush all flow director filter on port 0:: 3145 3146 testpmd> flush_flow_director 0 3147 3148flow_director_mask 3149~~~~~~~~~~~~~~~~~~ 3150 3151Set flow director's input masks:: 3152 3153 flow_director_mask (port_id) mode IP vlan (vlan_value) \ 3154 src_mask (ipv4_src) (ipv6_src) (src_port) \ 3155 dst_mask (ipv4_dst) (ipv6_dst) (dst_port) 3156 3157 flow_director_mask (port_id) mode MAC-VLAN vlan (vlan_value) 3158 3159 flow_director_mask (port_id) mode Tunnel vlan (vlan_value) \ 3160 mac (mac_value) tunnel-type (tunnel_type_value) \ 3161 tunnel-id (tunnel_id_value) 3162 3163Example, to set flow director mask on port 0:: 3164 3165 testpmd> flow_director_mask 0 mode IP vlan 0xefff \ 3166 src_mask 255.255.255.255 \ 3167 FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF \ 3168 dst_mask 255.255.255.255 \ 3169 FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF 3170 3171flow_director_flex_mask 3172~~~~~~~~~~~~~~~~~~~~~~~ 3173 3174set masks of flow director's flexible payload based on certain flow type:: 3175 3176 testpmd> flow_director_flex_mask (port_id) \ 3177 flow (none|ipv4-other|ipv4-frag|ipv4-tcp|ipv4-udp|ipv4-sctp| \ 3178 ipv6-other|ipv6-frag|ipv6-tcp|ipv6-udp|ipv6-sctp| \ 3179 l2_payload|all) (mask) 3180 3181Example, to set flow director's flex mask for all flow type on port 0:: 3182 3183 testpmd> flow_director_flex_mask 0 flow all \ 3184 (0xff,0xff,0,0,0,0,0,0,0,0,0,0,0,0,0,0) 3185 3186 3187flow_director_flex_payload 3188~~~~~~~~~~~~~~~~~~~~~~~~~~ 3189 3190Configure flexible payload selection:: 3191 3192 flow_director_flex_payload (port_id) (raw|l2|l3|l4) (config) 3193 3194For example, to select the first 16 bytes from the offset 4 (bytes) of packet's payload as flexible payload:: 3195 3196 testpmd> flow_director_flex_payload 0 l4 \ 3197 (4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19) 3198 3199get_sym_hash_ena_per_port 3200~~~~~~~~~~~~~~~~~~~~~~~~~ 3201 3202Get symmetric hash enable configuration per port:: 3203 3204 get_sym_hash_ena_per_port (port_id) 3205 3206For example, to get symmetric hash enable configuration of port 1:: 3207 3208 testpmd> get_sym_hash_ena_per_port 1 3209 3210set_sym_hash_ena_per_port 3211~~~~~~~~~~~~~~~~~~~~~~~~~ 3212 3213Set symmetric hash enable configuration per port to enable or disable:: 3214 3215 set_sym_hash_ena_per_port (port_id) (enable|disable) 3216 3217For example, to set symmetric hash enable configuration of port 1 to enable:: 3218 3219 testpmd> set_sym_hash_ena_per_port 1 enable 3220 3221get_hash_global_config 3222~~~~~~~~~~~~~~~~~~~~~~ 3223 3224Get the global configurations of hash filters:: 3225 3226 get_hash_global_config (port_id) 3227 3228For example, to get the global configurations of hash filters of port 1:: 3229 3230 testpmd> get_hash_global_config 1 3231 3232set_hash_global_config 3233~~~~~~~~~~~~~~~~~~~~~~ 3234 3235Set the global configurations of hash filters:: 3236 3237 set_hash_global_config (port_id) (toeplitz|simple_xor|default) \ 3238 (ipv4|ipv4-frag|ipv4-tcp|ipv4-udp|ipv4-sctp|ipv4-other|ipv6|ipv6-frag| \ 3239 ipv6-tcp|ipv6-udp|ipv6-sctp|ipv6-other|l2_payload|<flow_id>) \ 3240 (enable|disable) 3241 3242For example, to enable simple_xor for flow type of ipv6 on port 2:: 3243 3244 testpmd> set_hash_global_config 2 simple_xor ipv6 enable 3245 3246set_hash_input_set 3247~~~~~~~~~~~~~~~~~~ 3248 3249Set the input set for hash:: 3250 3251 set_hash_input_set (port_id) (ipv4-frag|ipv4-tcp|ipv4-udp|ipv4-sctp| \ 3252 ipv4-other|ipv6-frag|ipv6-tcp|ipv6-udp|ipv6-sctp|ipv6-other| \ 3253 l2_payload|<flow_id>) (ovlan|ivlan|src-ipv4|dst-ipv4|src-ipv6|dst-ipv6| \ 3254 ipv4-tos|ipv4-proto|ipv6-tc|ipv6-next-header|udp-src-port|udp-dst-port| \ 3255 tcp-src-port|tcp-dst-port|sctp-src-port|sctp-dst-port|sctp-veri-tag| \ 3256 udp-key|gre-key|fld-1st|fld-2nd|fld-3rd|fld-4th|fld-5th|fld-6th|fld-7th| \ 3257 fld-8th|none) (select|add) 3258 3259For example, to add source IP to hash input set for flow type of ipv4-udp on port 0:: 3260 3261 testpmd> set_hash_input_set 0 ipv4-udp src-ipv4 add 3262 3263set_fdir_input_set 3264~~~~~~~~~~~~~~~~~~ 3265 3266The Flow Director filters can match the different fields for different type of packet, i.e. specific input set 3267on per flow type and the flexible payload. This command can be used to change input set for each flow type. 3268 3269Set the input set for flow director:: 3270 3271 set_fdir_input_set (port_id) (ipv4-frag|ipv4-tcp|ipv4-udp|ipv4-sctp| \ 3272 ipv4-other|ipv6|ipv6-frag|ipv6-tcp|ipv6-udp|ipv6-sctp|ipv6-other| \ 3273 l2_payload|<flow_id>) (ivlan|ethertype|src-ipv4|dst-ipv4|src-ipv6|dst-ipv6| \ 3274 ipv4-tos|ipv4-proto|ipv4-ttl|ipv6-tc|ipv6-next-header|ipv6-hop-limits| \ 3275 tudp-src-port|udp-dst-port|cp-src-port|tcp-dst-port|sctp-src-port| \ 3276 sctp-dst-port|sctp-veri-tag|none) (select|add) 3277 3278For example to add source IP to FD input set for flow type of ipv4-udp on port 0:: 3279 3280 testpmd> set_fdir_input_set 0 ipv4-udp src-ipv4 add 3281 3282global_config 3283~~~~~~~~~~~~~ 3284 3285Set different GRE key length for input set:: 3286 3287 global_config (port_id) gre-key-len (number in bytes) 3288 3289For example to set GRE key length for input set to 4 bytes on port 0:: 3290 3291 testpmd> global_config 0 gre-key-len 4 3292 3293 3294.. _testpmd_rte_flow: 3295 3296Flow rules management 3297--------------------- 3298 3299Control of the generic flow API (*rte_flow*) is fully exposed through the 3300``flow`` command (validation, creation, destruction, queries and operation 3301modes). 3302 3303Considering *rte_flow* overlaps with all `Filter Functions`_, using both 3304features simultaneously may cause undefined side-effects and is therefore 3305not recommended. 3306 3307``flow`` syntax 3308~~~~~~~~~~~~~~~ 3309 3310Because the ``flow`` command uses dynamic tokens to handle the large number 3311of possible flow rules combinations, its behavior differs slightly from 3312other commands, in particular: 3313 3314- Pressing *?* or the *<tab>* key displays contextual help for the current 3315 token, not that of the entire command. 3316 3317- Optional and repeated parameters are supported (provided they are listed 3318 in the contextual help). 3319 3320The first parameter stands for the operation mode. Possible operations and 3321their general syntax are described below. They are covered in detail in the 3322following sections. 3323 3324- Check whether a flow rule can be created:: 3325 3326 flow validate {port_id} 3327 [group {group_id}] [priority {level}] [ingress] [egress] [transfer] 3328 pattern {item} [/ {item} [...]] / end 3329 actions {action} [/ {action} [...]] / end 3330 3331- Create a flow rule:: 3332 3333 flow create {port_id} 3334 [group {group_id}] [priority {level}] [ingress] [egress] [transfer] 3335 pattern {item} [/ {item} [...]] / end 3336 actions {action} [/ {action} [...]] / end 3337 3338- Destroy specific flow rules:: 3339 3340 flow destroy {port_id} rule {rule_id} [...] 3341 3342- Destroy all flow rules:: 3343 3344 flow flush {port_id} 3345 3346- Query an existing flow rule:: 3347 3348 flow query {port_id} {rule_id} {action} 3349 3350- List existing flow rules sorted by priority, filtered by group 3351 identifiers:: 3352 3353 flow list {port_id} [group {group_id}] [...] 3354 3355- Restrict ingress traffic to the defined flow rules:: 3356 3357 flow isolate {port_id} {boolean} 3358 3359Validating flow rules 3360~~~~~~~~~~~~~~~~~~~~~ 3361 3362``flow validate`` reports whether a flow rule would be accepted by the 3363underlying device in its current state but stops short of creating it. It is 3364bound to ``rte_flow_validate()``:: 3365 3366 flow validate {port_id} 3367 [group {group_id}] [priority {level}] [ingress] [egress] [transfer] 3368 pattern {item} [/ {item} [...]] / end 3369 actions {action} [/ {action} [...]] / end 3370 3371If successful, it will show:: 3372 3373 Flow rule validated 3374 3375Otherwise it will show an error message of the form:: 3376 3377 Caught error type [...] ([...]): [...] 3378 3379This command uses the same parameters as ``flow create``, their format is 3380described in `Creating flow rules`_. 3381 3382Check whether redirecting any Ethernet packet received on port 0 to RX queue 3383index 6 is supported:: 3384 3385 testpmd> flow validate 0 ingress pattern eth / end 3386 actions queue index 6 / end 3387 Flow rule validated 3388 testpmd> 3389 3390Port 0 does not support TCPv6 rules:: 3391 3392 testpmd> flow validate 0 ingress pattern eth / ipv6 / tcp / end 3393 actions drop / end 3394 Caught error type 9 (specific pattern item): Invalid argument 3395 testpmd> 3396 3397Creating flow rules 3398~~~~~~~~~~~~~~~~~~~ 3399 3400``flow create`` validates and creates the specified flow rule. It is bound 3401to ``rte_flow_create()``:: 3402 3403 flow create {port_id} 3404 [group {group_id}] [priority {level}] [ingress] [egress] [transfer] 3405 pattern {item} [/ {item} [...]] / end 3406 actions {action} [/ {action} [...]] / end 3407 3408If successful, it will return a flow rule ID usable with other commands:: 3409 3410 Flow rule #[...] created 3411 3412Otherwise it will show an error message of the form:: 3413 3414 Caught error type [...] ([...]): [...] 3415 3416Parameters describe in the following order: 3417 3418- Attributes (*group*, *priority*, *ingress*, *egress*, *transfer* tokens). 3419- A matching pattern, starting with the *pattern* token and terminated by an 3420 *end* pattern item. 3421- Actions, starting with the *actions* token and terminated by an *end* 3422 action. 3423 3424These translate directly to *rte_flow* objects provided as-is to the 3425underlying functions. 3426 3427The shortest valid definition only comprises mandatory tokens:: 3428 3429 testpmd> flow create 0 pattern end actions end 3430 3431Note that PMDs may refuse rules that essentially do nothing such as this 3432one. 3433 3434**All unspecified object values are automatically initialized to 0.** 3435 3436Attributes 3437^^^^^^^^^^ 3438 3439These tokens affect flow rule attributes (``struct rte_flow_attr``) and are 3440specified before the ``pattern`` token. 3441 3442- ``group {group id}``: priority group. 3443- ``priority {level}``: priority level within group. 3444- ``ingress``: rule applies to ingress traffic. 3445- ``egress``: rule applies to egress traffic. 3446- ``transfer``: apply rule directly to endpoints found in pattern. 3447 3448Each instance of an attribute specified several times overrides the previous 3449value as shown below (group 4 is used):: 3450 3451 testpmd> flow create 0 group 42 group 24 group 4 [...] 3452 3453Note that once enabled, ``ingress`` and ``egress`` cannot be disabled. 3454 3455While not specifying a direction is an error, some rules may allow both 3456simultaneously. 3457 3458Most rules affect RX therefore contain the ``ingress`` token:: 3459 3460 testpmd> flow create 0 ingress pattern [...] 3461 3462Matching pattern 3463^^^^^^^^^^^^^^^^ 3464 3465A matching pattern starts after the ``pattern`` token. It is made of pattern 3466items and is terminated by a mandatory ``end`` item. 3467 3468Items are named after their type (*RTE_FLOW_ITEM_TYPE_* from ``enum 3469rte_flow_item_type``). 3470 3471The ``/`` token is used as a separator between pattern items as shown 3472below:: 3473 3474 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / end [...] 3475 3476Note that protocol items like these must be stacked from lowest to highest 3477layer to make sense. For instance, the following rule is either invalid or 3478unlikely to match any packet:: 3479 3480 testpmd> flow create 0 ingress pattern eth / udp / ipv4 / end [...] 3481 3482More information on these restrictions can be found in the *rte_flow* 3483documentation. 3484 3485Several items support additional specification structures, for example 3486``ipv4`` allows specifying source and destination addresses as follows:: 3487 3488 testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.1.1.1 3489 dst is 10.2.0.0 / end [...] 3490 3491This rule matches all IPv4 traffic with the specified properties. 3492 3493In this example, ``src`` and ``dst`` are field names of the underlying 3494``struct rte_flow_item_ipv4`` object. All item properties can be specified 3495in a similar fashion. 3496 3497The ``is`` token means that the subsequent value must be matched exactly, 3498and assigns ``spec`` and ``mask`` fields in ``struct rte_flow_item`` 3499accordingly. Possible assignment tokens are: 3500 3501- ``is``: match value perfectly (with full bit-mask). 3502- ``spec``: match value according to configured bit-mask. 3503- ``last``: specify upper bound to establish a range. 3504- ``mask``: specify bit-mask with relevant bits set to one. 3505- ``prefix``: generate bit-mask with <prefix-length> most-significant bits set to one. 3506 3507These yield identical results:: 3508 3509 ipv4 src is 10.1.1.1 3510 3511:: 3512 3513 ipv4 src spec 10.1.1.1 src mask 255.255.255.255 3514 3515:: 3516 3517 ipv4 src spec 10.1.1.1 src prefix 32 3518 3519:: 3520 3521 ipv4 src is 10.1.1.1 src last 10.1.1.1 # range with a single value 3522 3523:: 3524 3525 ipv4 src is 10.1.1.1 src last 0 # 0 disables range 3526 3527Inclusive ranges can be defined with ``last``:: 3528 3529 ipv4 src is 10.1.1.1 src last 10.2.3.4 # 10.1.1.1 to 10.2.3.4 3530 3531Note that ``mask`` affects both ``spec`` and ``last``:: 3532 3533 ipv4 src is 10.1.1.1 src last 10.2.3.4 src mask 255.255.0.0 3534 # matches 10.1.0.0 to 10.2.255.255 3535 3536Properties can be modified multiple times:: 3537 3538 ipv4 src is 10.1.1.1 src is 10.1.2.3 src is 10.2.3.4 # matches 10.2.3.4 3539 3540:: 3541 3542 ipv4 src is 10.1.1.1 src prefix 24 src prefix 16 # matches 10.1.0.0/16 3543 3544Pattern items 3545^^^^^^^^^^^^^ 3546 3547This section lists supported pattern items and their attributes, if any. 3548 3549- ``end``: end list of pattern items. 3550 3551- ``void``: no-op pattern item. 3552 3553- ``invert``: perform actions when pattern does not match. 3554 3555- ``any``: match any protocol for the current layer. 3556 3557 - ``num {unsigned}``: number of layers covered. 3558 3559- ``pf``: match traffic from/to the physical function. 3560 3561- ``vf``: match traffic from/to a virtual function ID. 3562 3563 - ``id {unsigned}``: VF ID. 3564 3565- ``phy_port``: match traffic from/to a specific physical port. 3566 3567 - ``index {unsigned}``: physical port index. 3568 3569- ``port_id``: match traffic from/to a given DPDK port ID. 3570 3571 - ``id {unsigned}``: DPDK port ID. 3572 3573- ``mark``: match value set in previously matched flow rule using the mark action. 3574 3575 - ``id {unsigned}``: arbitrary integer value. 3576 3577- ``raw``: match an arbitrary byte string. 3578 3579 - ``relative {boolean}``: look for pattern after the previous item. 3580 - ``search {boolean}``: search pattern from offset (see also limit). 3581 - ``offset {integer}``: absolute or relative offset for pattern. 3582 - ``limit {unsigned}``: search area limit for start of pattern. 3583 - ``pattern {string}``: byte string to look for. 3584 3585- ``eth``: match Ethernet header. 3586 3587 - ``dst {MAC-48}``: destination MAC. 3588 - ``src {MAC-48}``: source MAC. 3589 - ``type {unsigned}``: EtherType or TPID. 3590 3591- ``vlan``: match 802.1Q/ad VLAN tag. 3592 3593 - ``tci {unsigned}``: tag control information. 3594 - ``pcp {unsigned}``: priority code point. 3595 - ``dei {unsigned}``: drop eligible indicator. 3596 - ``vid {unsigned}``: VLAN identifier. 3597 - ``inner_type {unsigned}``: inner EtherType or TPID. 3598 3599- ``ipv4``: match IPv4 header. 3600 3601 - ``tos {unsigned}``: type of service. 3602 - ``ttl {unsigned}``: time to live. 3603 - ``proto {unsigned}``: next protocol ID. 3604 - ``src {ipv4 address}``: source address. 3605 - ``dst {ipv4 address}``: destination address. 3606 3607- ``ipv6``: match IPv6 header. 3608 3609 - ``tc {unsigned}``: traffic class. 3610 - ``flow {unsigned}``: flow label. 3611 - ``proto {unsigned}``: protocol (next header). 3612 - ``hop {unsigned}``: hop limit. 3613 - ``src {ipv6 address}``: source address. 3614 - ``dst {ipv6 address}``: destination address. 3615 3616- ``icmp``: match ICMP header. 3617 3618 - ``type {unsigned}``: ICMP packet type. 3619 - ``code {unsigned}``: ICMP packet code. 3620 3621- ``udp``: match UDP header. 3622 3623 - ``src {unsigned}``: UDP source port. 3624 - ``dst {unsigned}``: UDP destination port. 3625 3626- ``tcp``: match TCP header. 3627 3628 - ``src {unsigned}``: TCP source port. 3629 - ``dst {unsigned}``: TCP destination port. 3630 3631- ``sctp``: match SCTP header. 3632 3633 - ``src {unsigned}``: SCTP source port. 3634 - ``dst {unsigned}``: SCTP destination port. 3635 - ``tag {unsigned}``: validation tag. 3636 - ``cksum {unsigned}``: checksum. 3637 3638- ``vxlan``: match VXLAN header. 3639 3640 - ``vni {unsigned}``: VXLAN identifier. 3641 3642- ``e_tag``: match IEEE 802.1BR E-Tag header. 3643 3644 - ``grp_ecid_b {unsigned}``: GRP and E-CID base. 3645 3646- ``nvgre``: match NVGRE header. 3647 3648 - ``tni {unsigned}``: virtual subnet ID. 3649 3650- ``mpls``: match MPLS header. 3651 3652 - ``label {unsigned}``: MPLS label. 3653 3654- ``gre``: match GRE header. 3655 3656 - ``protocol {unsigned}``: protocol type. 3657 3658- ``fuzzy``: fuzzy pattern match, expect faster than default. 3659 3660 - ``thresh {unsigned}``: accuracy threshold. 3661 3662- ``gtp``, ``gtpc``, ``gtpu``: match GTPv1 header. 3663 3664 - ``teid {unsigned}``: tunnel endpoint identifier. 3665 3666- ``geneve``: match GENEVE header. 3667 3668 - ``vni {unsigned}``: virtual network identifier. 3669 - ``protocol {unsigned}``: protocol type. 3670 3671- ``vxlan-gpe``: match VXLAN-GPE header. 3672 3673 - ``vni {unsigned}``: VXLAN-GPE identifier. 3674 3675- ``arp_eth_ipv4``: match ARP header for Ethernet/IPv4. 3676 3677 - ``sha {MAC-48}``: sender hardware address. 3678 - ``spa {ipv4 address}``: sender IPv4 address. 3679 - ``tha {MAC-48}``: target hardware address. 3680 - ``tpa {ipv4 address}``: target IPv4 address. 3681 3682- ``ipv6_ext``: match presence of any IPv6 extension header. 3683 3684 - ``next_hdr {unsigned}``: next header. 3685 3686- ``icmp6``: match any ICMPv6 header. 3687 3688 - ``type {unsigned}``: ICMPv6 type. 3689 - ``code {unsigned}``: ICMPv6 code. 3690 3691- ``icmp6_nd_ns``: match ICMPv6 neighbor discovery solicitation. 3692 3693 - ``target_addr {ipv6 address}``: target address. 3694 3695- ``icmp6_nd_na``: match ICMPv6 neighbor discovery advertisement. 3696 3697 - ``target_addr {ipv6 address}``: target address. 3698 3699- ``icmp6_nd_opt``: match presence of any ICMPv6 neighbor discovery option. 3700 3701 - ``type {unsigned}``: ND option type. 3702 3703- ``icmp6_nd_opt_sla_eth``: match ICMPv6 neighbor discovery source Ethernet 3704 link-layer address option. 3705 3706 - ``sla {MAC-48}``: source Ethernet LLA. 3707 3708- ``icmp6_nd_opt_sla_eth``: match ICMPv6 neighbor discovery target Ethernet 3709 link-layer address option. 3710 3711 - ``tla {MAC-48}``: target Ethernet LLA. 3712 3713- ``meta``: match application specific metadata. 3714 3715 - ``data {unsigned}``: metadata value. 3716 3717Actions list 3718^^^^^^^^^^^^ 3719 3720A list of actions starts after the ``actions`` token in the same fashion as 3721`Matching pattern`_; actions are separated by ``/`` tokens and the list is 3722terminated by a mandatory ``end`` action. 3723 3724Actions are named after their type (*RTE_FLOW_ACTION_TYPE_* from ``enum 3725rte_flow_action_type``). 3726 3727Dropping all incoming UDPv4 packets can be expressed as follows:: 3728 3729 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / end 3730 actions drop / end 3731 3732Several actions have configurable properties which must be specified when 3733there is no valid default value. For example, ``queue`` requires a target 3734queue index. 3735 3736This rule redirects incoming UDPv4 traffic to queue index 6:: 3737 3738 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / end 3739 actions queue index 6 / end 3740 3741While this one could be rejected by PMDs (unspecified queue index):: 3742 3743 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / end 3744 actions queue / end 3745 3746As defined by *rte_flow*, the list is not ordered, all actions of a given 3747rule are performed simultaneously. These are equivalent:: 3748 3749 queue index 6 / void / mark id 42 / end 3750 3751:: 3752 3753 void / mark id 42 / queue index 6 / end 3754 3755All actions in a list should have different types, otherwise only the last 3756action of a given type is taken into account:: 3757 3758 queue index 4 / queue index 5 / queue index 6 / end # will use queue 6 3759 3760:: 3761 3762 drop / drop / drop / end # drop is performed only once 3763 3764:: 3765 3766 mark id 42 / queue index 3 / mark id 24 / end # mark will be 24 3767 3768Considering they are performed simultaneously, opposite and overlapping 3769actions can sometimes be combined when the end result is unambiguous:: 3770 3771 drop / queue index 6 / end # drop has no effect 3772 3773:: 3774 3775 queue index 6 / rss queues 6 7 8 / end # queue has no effect 3776 3777:: 3778 3779 drop / passthru / end # drop has no effect 3780 3781Note that PMDs may still refuse such combinations. 3782 3783Actions 3784^^^^^^^ 3785 3786This section lists supported actions and their attributes, if any. 3787 3788- ``end``: end list of actions. 3789 3790- ``void``: no-op action. 3791 3792- ``passthru``: let subsequent rule process matched packets. 3793 3794- ``jump``: redirect traffic to group on device. 3795 3796 - ``group {unsigned}``: group to redirect to. 3797 3798- ``mark``: attach 32 bit value to packets. 3799 3800 - ``id {unsigned}``: 32 bit value to return with packets. 3801 3802- ``flag``: flag packets. 3803 3804- ``queue``: assign packets to a given queue index. 3805 3806 - ``index {unsigned}``: queue index to use. 3807 3808- ``drop``: drop packets (note: passthru has priority). 3809 3810- ``count``: enable counters for this rule. 3811 3812- ``rss``: spread packets among several queues. 3813 3814 - ``func {hash function}``: RSS hash function to apply, allowed tokens are 3815 the same as `set_hash_global_config`_. 3816 3817 - ``level {unsigned}``: encapsulation level for ``types``. 3818 3819 - ``types [{RSS hash type} [...]] end``: specific RSS hash types, allowed 3820 tokens are the same as `set_hash_input_set`_, except that an empty list 3821 does not disable RSS but instead requests unspecified "best-effort" 3822 settings. 3823 3824 - ``key {string}``: RSS hash key, overrides ``key_len``. 3825 3826 - ``key_len {unsigned}``: RSS hash key length in bytes, can be used in 3827 conjunction with ``key`` to pad or truncate it. 3828 3829 - ``queues [{unsigned} [...]] end``: queue indices to use. 3830 3831- ``pf``: direct traffic to physical function. 3832 3833- ``vf``: direct traffic to a virtual function ID. 3834 3835 - ``original {boolean}``: use original VF ID if possible. 3836 - ``id {unsigned}``: VF ID. 3837 3838- ``phy_port``: direct packets to physical port index. 3839 3840 - ``original {boolean}``: use original port index if possible. 3841 - ``index {unsigned}``: physical port index. 3842 3843- ``port_id``: direct matching traffic to a given DPDK port ID. 3844 3845 - ``original {boolean}``: use original DPDK port ID if possible. 3846 - ``id {unsigned}``: DPDK port ID. 3847 3848- ``of_set_mpls_ttl``: OpenFlow's ``OFPAT_SET_MPLS_TTL``. 3849 3850 - ``mpls_ttl``: MPLS TTL. 3851 3852- ``of_dec_mpls_ttl``: OpenFlow's ``OFPAT_DEC_MPLS_TTL``. 3853 3854- ``of_set_nw_ttl``: OpenFlow's ``OFPAT_SET_NW_TTL``. 3855 3856 - ``nw_ttl``: IP TTL. 3857 3858- ``of_dec_nw_ttl``: OpenFlow's ``OFPAT_DEC_NW_TTL``. 3859 3860- ``of_copy_ttl_out``: OpenFlow's ``OFPAT_COPY_TTL_OUT``. 3861 3862- ``of_copy_ttl_in``: OpenFlow's ``OFPAT_COPY_TTL_IN``. 3863 3864- ``of_pop_vlan``: OpenFlow's ``OFPAT_POP_VLAN``. 3865 3866- ``of_push_vlan``: OpenFlow's ``OFPAT_PUSH_VLAN``. 3867 3868 - ``ethertype``: Ethertype. 3869 3870- ``of_set_vlan_vid``: OpenFlow's ``OFPAT_SET_VLAN_VID``. 3871 3872 - ``vlan_vid``: VLAN id. 3873 3874- ``of_set_vlan_pcp``: OpenFlow's ``OFPAT_SET_VLAN_PCP``. 3875 3876 - ``vlan_pcp``: VLAN priority. 3877 3878- ``of_pop_mpls``: OpenFlow's ``OFPAT_POP_MPLS``. 3879 3880 - ``ethertype``: Ethertype. 3881 3882- ``of_push_mpls``: OpenFlow's ``OFPAT_PUSH_MPLS``. 3883 3884 - ``ethertype``: Ethertype. 3885 3886- ``vxlan_encap``: Performs a VXLAN encapsulation, outer layer configuration 3887 is done through `Config VXLAN Encap outer layers`_. 3888 3889- ``vxlan_decap``: Performs a decapsulation action by stripping all headers of 3890 the VXLAN tunnel network overlay from the matched flow. 3891 3892- ``nvgre_encap``: Performs a NVGRE encapsulation, outer layer configuration 3893 is done through `Config NVGRE Encap outer layers`_. 3894 3895- ``nvgre_decap``: Performs a decapsulation action by stripping all headers of 3896 the NVGRE tunnel network overlay from the matched flow. 3897 3898- ``l2_encap``: Performs a L2 encapsulation, L2 configuration 3899 is done through `Config L2 Encap`_. 3900 3901- ``l2_decap``: Performs a L2 decapsulation, L2 configuration 3902 is done through `Config L2 Decap`_. 3903 3904- ``mplsogre_encap``: Performs a MPLSoGRE encapsulation, outer layer 3905 configuration is done through `Config MPLSoGRE Encap outer layers`_. 3906 3907- ``mplsogre_decap``: Performs a MPLSoGRE decapsulation, outer layer 3908 configuration is done through `Config MPLSoGRE Decap outer layers`_. 3909 3910- ``mplsoudp_encap``: Performs a MPLSoUDP encapsulation, outer layer 3911 configuration is done through `Config MPLSoUDP Encap outer layers`_. 3912 3913- ``mplsoudp_decap``: Performs a MPLSoUDP decapsulation, outer layer 3914 configuration is done through `Config MPLSoUDP Decap outer layers`_. 3915 3916- ``set_ipv4_src``: Set a new IPv4 source address in the outermost IPv4 header. 3917 3918 - ``ipv4_addr``: New IPv4 source address. 3919 3920- ``set_ipv4_dst``: Set a new IPv4 destination address in the outermost IPv4 3921 header. 3922 3923 - ``ipv4_addr``: New IPv4 destination address. 3924 3925- ``set_ipv6_src``: Set a new IPv6 source address in the outermost IPv6 header. 3926 3927 - ``ipv6_addr``: New IPv6 source address. 3928 3929- ``set_ipv6_dst``: Set a new IPv6 destination address in the outermost IPv6 3930 header. 3931 3932 - ``ipv6_addr``: New IPv6 destination address. 3933 3934- ``of_set_tp_src``: Set a new source port number in the outermost TCP/UDP 3935 header. 3936 3937 - ``port``: New TCP/UDP source port number. 3938 3939- ``of_set_tp_dst``: Set a new destination port number in the outermost TCP/UDP 3940 header. 3941 3942 - ``port``: New TCP/UDP destination port number. 3943 3944- ``mac_swap``: Swap the source and destination MAC addresses in the outermost 3945 Ethernet header. 3946 3947- ``dec_ttl``: Performs a decrease TTL value action 3948 3949- ``set_ttl``: Set TTL value with specificed value 3950 - ``ttl_value {unsigned}``: The new TTL value to be set 3951 3952- ``set_mac_src``: set source MAC address 3953 3954 - ``mac_addr {MAC-48}``: new source MAC address 3955 3956- ``set_mac_dst``: set destination MAC address 3957 3958 - ``mac_addr {MAC-48}``: new destination MAC address 3959 3960Destroying flow rules 3961~~~~~~~~~~~~~~~~~~~~~ 3962 3963``flow destroy`` destroys one or more rules from their rule ID (as returned 3964by ``flow create``), this command calls ``rte_flow_destroy()`` as many 3965times as necessary:: 3966 3967 flow destroy {port_id} rule {rule_id} [...] 3968 3969If successful, it will show:: 3970 3971 Flow rule #[...] destroyed 3972 3973It does not report anything for rule IDs that do not exist. The usual error 3974message is shown when a rule cannot be destroyed:: 3975 3976 Caught error type [...] ([...]): [...] 3977 3978``flow flush`` destroys all rules on a device and does not take extra 3979arguments. It is bound to ``rte_flow_flush()``:: 3980 3981 flow flush {port_id} 3982 3983Any errors are reported as above. 3984 3985Creating several rules and destroying them:: 3986 3987 testpmd> flow create 0 ingress pattern eth / ipv6 / end 3988 actions queue index 2 / end 3989 Flow rule #0 created 3990 testpmd> flow create 0 ingress pattern eth / ipv4 / end 3991 actions queue index 3 / end 3992 Flow rule #1 created 3993 testpmd> flow destroy 0 rule 0 rule 1 3994 Flow rule #1 destroyed 3995 Flow rule #0 destroyed 3996 testpmd> 3997 3998The same result can be achieved using ``flow flush``:: 3999 4000 testpmd> flow create 0 ingress pattern eth / ipv6 / end 4001 actions queue index 2 / end 4002 Flow rule #0 created 4003 testpmd> flow create 0 ingress pattern eth / ipv4 / end 4004 actions queue index 3 / end 4005 Flow rule #1 created 4006 testpmd> flow flush 0 4007 testpmd> 4008 4009Non-existent rule IDs are ignored:: 4010 4011 testpmd> flow create 0 ingress pattern eth / ipv6 / end 4012 actions queue index 2 / end 4013 Flow rule #0 created 4014 testpmd> flow create 0 ingress pattern eth / ipv4 / end 4015 actions queue index 3 / end 4016 Flow rule #1 created 4017 testpmd> flow destroy 0 rule 42 rule 10 rule 2 4018 testpmd> 4019 testpmd> flow destroy 0 rule 0 4020 Flow rule #0 destroyed 4021 testpmd> 4022 4023Querying flow rules 4024~~~~~~~~~~~~~~~~~~~ 4025 4026``flow query`` queries a specific action of a flow rule having that 4027ability. Such actions collect information that can be reported using this 4028command. It is bound to ``rte_flow_query()``:: 4029 4030 flow query {port_id} {rule_id} {action} 4031 4032If successful, it will display either the retrieved data for known actions 4033or the following message:: 4034 4035 Cannot display result for action type [...] ([...]) 4036 4037Otherwise, it will complain either that the rule does not exist or that some 4038error occurred:: 4039 4040 Flow rule #[...] not found 4041 4042:: 4043 4044 Caught error type [...] ([...]): [...] 4045 4046Currently only the ``count`` action is supported. This action reports the 4047number of packets that hit the flow rule and the total number of bytes. Its 4048output has the following format:: 4049 4050 count: 4051 hits_set: [...] # whether "hits" contains a valid value 4052 bytes_set: [...] # whether "bytes" contains a valid value 4053 hits: [...] # number of packets 4054 bytes: [...] # number of bytes 4055 4056Querying counters for TCPv6 packets redirected to queue 6:: 4057 4058 testpmd> flow create 0 ingress pattern eth / ipv6 / tcp / end 4059 actions queue index 6 / count / end 4060 Flow rule #4 created 4061 testpmd> flow query 0 4 count 4062 count: 4063 hits_set: 1 4064 bytes_set: 0 4065 hits: 386446 4066 bytes: 0 4067 testpmd> 4068 4069Listing flow rules 4070~~~~~~~~~~~~~~~~~~ 4071 4072``flow list`` lists existing flow rules sorted by priority and optionally 4073filtered by group identifiers:: 4074 4075 flow list {port_id} [group {group_id}] [...] 4076 4077This command only fails with the following message if the device does not 4078exist:: 4079 4080 Invalid port [...] 4081 4082Output consists of a header line followed by a short description of each 4083flow rule, one per line. There is no output at all when no flow rules are 4084configured on the device:: 4085 4086 ID Group Prio Attr Rule 4087 [...] [...] [...] [...] [...] 4088 4089``Attr`` column flags: 4090 4091- ``i`` for ``ingress``. 4092- ``e`` for ``egress``. 4093 4094Creating several flow rules and listing them:: 4095 4096 testpmd> flow create 0 ingress pattern eth / ipv4 / end 4097 actions queue index 6 / end 4098 Flow rule #0 created 4099 testpmd> flow create 0 ingress pattern eth / ipv6 / end 4100 actions queue index 2 / end 4101 Flow rule #1 created 4102 testpmd> flow create 0 priority 5 ingress pattern eth / ipv4 / udp / end 4103 actions rss queues 6 7 8 end / end 4104 Flow rule #2 created 4105 testpmd> flow list 0 4106 ID Group Prio Attr Rule 4107 0 0 0 i- ETH IPV4 => QUEUE 4108 1 0 0 i- ETH IPV6 => QUEUE 4109 2 0 5 i- ETH IPV4 UDP => RSS 4110 testpmd> 4111 4112Rules are sorted by priority (i.e. group ID first, then priority level):: 4113 4114 testpmd> flow list 1 4115 ID Group Prio Attr Rule 4116 0 0 0 i- ETH => COUNT 4117 6 0 500 i- ETH IPV6 TCP => DROP COUNT 4118 5 0 1000 i- ETH IPV6 ICMP => QUEUE 4119 1 24 0 i- ETH IPV4 UDP => QUEUE 4120 4 24 10 i- ETH IPV4 TCP => DROP 4121 3 24 20 i- ETH IPV4 => DROP 4122 2 24 42 i- ETH IPV4 UDP => QUEUE 4123 7 63 0 i- ETH IPV6 UDP VXLAN => MARK QUEUE 4124 testpmd> 4125 4126Output can be limited to specific groups:: 4127 4128 testpmd> flow list 1 group 0 group 63 4129 ID Group Prio Attr Rule 4130 0 0 0 i- ETH => COUNT 4131 6 0 500 i- ETH IPV6 TCP => DROP COUNT 4132 5 0 1000 i- ETH IPV6 ICMP => QUEUE 4133 7 63 0 i- ETH IPV6 UDP VXLAN => MARK QUEUE 4134 testpmd> 4135 4136Toggling isolated mode 4137~~~~~~~~~~~~~~~~~~~~~~ 4138 4139``flow isolate`` can be used to tell the underlying PMD that ingress traffic 4140must only be injected from the defined flow rules; that no default traffic 4141is expected outside those rules and the driver is free to assign more 4142resources to handle them. It is bound to ``rte_flow_isolate()``:: 4143 4144 flow isolate {port_id} {boolean} 4145 4146If successful, enabling or disabling isolated mode shows either:: 4147 4148 Ingress traffic on port [...] 4149 is now restricted to the defined flow rules 4150 4151Or:: 4152 4153 Ingress traffic on port [...] 4154 is not restricted anymore to the defined flow rules 4155 4156Otherwise, in case of error:: 4157 4158 Caught error type [...] ([...]): [...] 4159 4160Mainly due to its side effects, PMDs supporting this mode may not have the 4161ability to toggle it more than once without reinitializing affected ports 4162first (e.g. by exiting testpmd). 4163 4164Enabling isolated mode:: 4165 4166 testpmd> flow isolate 0 true 4167 Ingress traffic on port 0 is now restricted to the defined flow rules 4168 testpmd> 4169 4170Disabling isolated mode:: 4171 4172 testpmd> flow isolate 0 false 4173 Ingress traffic on port 0 is not restricted anymore to the defined flow rules 4174 testpmd> 4175 4176Sample QinQ flow rules 4177~~~~~~~~~~~~~~~~~~~~~~ 4178 4179Before creating QinQ rule(s) the following commands should be issued to enable QinQ:: 4180 4181 testpmd> port stop 0 4182 testpmd> vlan set qinq on 0 4183 4184The above command sets the inner and outer TPID's to 0x8100. 4185 4186To change the TPID's the following commands should be used:: 4187 4188 testpmd> vlan set outer tpid 0xa100 0 4189 testpmd> vlan set inner tpid 0x9100 0 4190 testpmd> port start 0 4191 4192Validate and create a QinQ rule on port 0 to steer traffic to a VF queue in a VM. 4193 4194:: 4195 4196 testpmd> flow validate 0 ingress pattern eth / vlan tci is 123 / 4197 vlan tci is 456 / end actions vf id 1 / queue index 0 / end 4198 Flow rule #0 validated 4199 4200 testpmd> flow create 0 ingress pattern eth / vlan tci is 4 / 4201 vlan tci is 456 / end actions vf id 123 / queue index 0 / end 4202 Flow rule #0 created 4203 4204 testpmd> flow list 0 4205 ID Group Prio Attr Rule 4206 0 0 0 i- ETH VLAN VLAN=>VF QUEUE 4207 4208Validate and create a QinQ rule on port 0 to steer traffic to a queue on the host. 4209 4210:: 4211 4212 testpmd> flow validate 0 ingress pattern eth / vlan tci is 321 / 4213 vlan tci is 654 / end actions pf / queue index 0 / end 4214 Flow rule #1 validated 4215 4216 testpmd> flow create 0 ingress pattern eth / vlan tci is 321 / 4217 vlan tci is 654 / end actions pf / queue index 1 / end 4218 Flow rule #1 created 4219 4220 testpmd> flow list 0 4221 ID Group Prio Attr Rule 4222 0 0 0 i- ETH VLAN VLAN=>VF QUEUE 4223 1 0 0 i- ETH VLAN VLAN=>PF QUEUE 4224 4225Sample VXLAN encapsulation rule 4226~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4227 4228VXLAN encapsulation outer layer has default value pre-configured in testpmd 4229source code, those can be changed by using the following commands 4230 4231IPv4 VXLAN outer header:: 4232 4233 testpmd> set vxlan ip-version ipv4 vni 4 udp-src 4 udp-dst 4 ip-src 127.0.0.1 4234 ip-dst 128.0.0.1 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4235 testpmd> flow create 0 ingress pattern end actions vxlan_encap / 4236 queue index 0 / end 4237 4238 testpmd> set vxlan-with-vlan ip-version ipv4 vni 4 udp-src 4 udp-dst 4 ip-src 4239 127.0.0.1 ip-dst 128.0.0.1 vlan-tci 34 eth-src 11:11:11:11:11:11 4240 eth-dst 22:22:22:22:22:22 4241 testpmd> flow create 0 ingress pattern end actions vxlan_encap / 4242 queue index 0 / end 4243 4244IPv6 VXLAN outer header:: 4245 4246 testpmd> set vxlan ip-version ipv6 vni 4 udp-src 4 udp-dst 4 ip-src ::1 4247 ip-dst ::2222 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4248 testpmd> flow create 0 ingress pattern end actions vxlan_encap / 4249 queue index 0 / end 4250 4251 testpmd> set vxlan-with-vlan ip-version ipv6 vni 4 udp-src 4 udp-dst 4 4252 ip-src ::1 ip-dst ::2222 vlan-tci 34 eth-src 11:11:11:11:11:11 4253 eth-dst 22:22:22:22:22:22 4254 testpmd> flow create 0 ingress pattern end actions vxlan_encap / 4255 queue index 0 / end 4256 4257Sample NVGRE encapsulation rule 4258~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4259 4260NVGRE encapsulation outer layer has default value pre-configured in testpmd 4261source code, those can be changed by using the following commands 4262 4263IPv4 NVGRE outer header:: 4264 4265 testpmd> set nvgre ip-version ipv4 tni 4 ip-src 127.0.0.1 ip-dst 128.0.0.1 4266 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4267 testpmd> flow create 0 ingress pattern end actions nvgre_encap / 4268 queue index 0 / end 4269 4270 testpmd> set nvgre-with-vlan ip-version ipv4 tni 4 ip-src 127.0.0.1 4271 ip-dst 128.0.0.1 vlan-tci 34 eth-src 11:11:11:11:11:11 4272 eth-dst 22:22:22:22:22:22 4273 testpmd> flow create 0 ingress pattern end actions nvgre_encap / 4274 queue index 0 / end 4275 4276IPv6 NVGRE outer header:: 4277 4278 testpmd> set nvgre ip-version ipv6 tni 4 ip-src ::1 ip-dst ::2222 4279 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4280 testpmd> flow create 0 ingress pattern end actions nvgre_encap / 4281 queue index 0 / end 4282 4283 testpmd> set nvgre-with-vlan ip-version ipv6 tni 4 ip-src ::1 ip-dst ::2222 4284 vlan-tci 34 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4285 testpmd> flow create 0 ingress pattern end actions nvgre_encap / 4286 queue index 0 / end 4287 4288Sample L2 encapsulation rule 4289~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4290 4291L2 encapsulation has default value pre-configured in testpmd 4292source code, those can be changed by using the following commands 4293 4294L2 header:: 4295 4296 testpmd> set l2_encap ip-version ipv4 4297 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4298 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / mpls / end actions 4299 mplsoudp_decap / l2_encap / end 4300 4301L2 with VXLAN header:: 4302 4303 testpmd> set l2_encap-with-vlan ip-version ipv4 vlan-tci 34 4304 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4305 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / mpls / end actions 4306 mplsoudp_decap / l2_encap / end 4307 4308Sample L2 decapsulation rule 4309~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4310 4311L2 decapsulation has default value pre-configured in testpmd 4312source code, those can be changed by using the following commands 4313 4314L2 header:: 4315 4316 testpmd> set l2_decap 4317 testpmd> flow create 0 egress pattern eth / end actions l2_decap / mplsoudp_encap / 4318 queue index 0 / end 4319 4320L2 with VXLAN header:: 4321 4322 testpmd> set l2_encap-with-vlan 4323 testpmd> flow create 0 egress pattern eth / end actions l2_encap / mplsoudp_encap / 4324 queue index 0 / end 4325 4326Sample MPLSoGRE encapsulation rule 4327~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4328 4329MPLSoGRE encapsulation outer layer has default value pre-configured in testpmd 4330source code, those can be changed by using the following commands 4331 4332IPv4 MPLSoGRE outer header:: 4333 4334 testpmd> set mplsogre_encap ip-version ipv4 label 4 4335 ip-src 127.0.0.1 ip-dst 128.0.0.1 eth-src 11:11:11:11:11:11 4336 eth-dst 22:22:22:22:22:22 4337 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4338 mplsogre_encap / end 4339 4340IPv4 MPLSoGRE with VLAN outer header:: 4341 4342 testpmd> set mplsogre_encap-with-vlan ip-version ipv4 label 4 4343 ip-src 127.0.0.1 ip-dst 128.0.0.1 vlan-tci 34 4344 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4345 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4346 mplsogre_encap / end 4347 4348IPv6 MPLSoGRE outer header:: 4349 4350 testpmd> set mplsogre_encap ip-version ipv6 mask 4 4351 ip-src ::1 ip-dst ::2222 eth-src 11:11:11:11:11:11 4352 eth-dst 22:22:22:22:22:22 4353 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4354 mplsogre_encap / end 4355 4356IPv6 MPLSoGRE with VLAN outer header:: 4357 4358 testpmd> set mplsogre_encap-with-vlan ip-version ipv6 mask 4 4359 ip-src ::1 ip-dst ::2222 vlan-tci 34 4360 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4361 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4362 mplsogre_encap / end 4363 4364Sample MPLSoGRE decapsulation rule 4365~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4366 4367MPLSoGRE decapsulation outer layer has default value pre-configured in testpmd 4368source code, those can be changed by using the following commands 4369 4370IPv4 MPLSoGRE outer header:: 4371 4372 testpmd> set mplsogre_decap ip-version ipv4 4373 testpmd> flow create 0 ingress pattern eth / ipv4 / gre / mpls / end actions 4374 mplsogre_decap / l2_encap / end 4375 4376IPv4 MPLSoGRE with VLAN outer header:: 4377 4378 testpmd> set mplsogre_decap-with-vlan ip-version ipv4 4379 testpmd> flow create 0 ingress pattern eth / vlan / ipv4 / gre / mpls / end 4380 actions mplsogre_decap / l2_encap / end 4381 4382IPv6 MPLSoGRE outer header:: 4383 4384 testpmd> set mplsogre_decap ip-version ipv6 4385 testpmd> flow create 0 ingress pattern eth / ipv6 / gre / mpls / end 4386 actions mplsogre_decap / l2_encap / end 4387 4388IPv6 MPLSoGRE with VLAN outer header:: 4389 4390 testpmd> set mplsogre_decap-with-vlan ip-version ipv6 4391 testpmd> flow create 0 ingress pattern eth / vlan / ipv6 / gre / mpls / end 4392 actions mplsogre_decap / l2_encap / end 4393 4394Sample MPLSoUDP encapsulation rule 4395~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4396 4397MPLSoUDP encapsulation outer layer has default value pre-configured in testpmd 4398source code, those can be changed by using the following commands 4399 4400IPv4 MPLSoUDP outer header:: 4401 4402 testpmd> set mplsoudp_encap ip-version ipv4 label 4 udp-src 5 udp-dst 10 4403 ip-src 127.0.0.1 ip-dst 128.0.0.1 eth-src 11:11:11:11:11:11 4404 eth-dst 22:22:22:22:22:22 4405 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4406 mplsoudp_encap / end 4407 4408IPv4 MPLSoUDP with VLAN outer header:: 4409 4410 testpmd> set mplsoudp_encap-with-vlan ip-version ipv4 label 4 udp-src 5 4411 udp-dst 10 ip-src 127.0.0.1 ip-dst 128.0.0.1 vlan-tci 34 4412 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4413 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4414 mplsoudp_encap / end 4415 4416IPv6 MPLSoUDP outer header:: 4417 4418 testpmd> set mplsoudp_encap ip-version ipv6 mask 4 udp-src 5 udp-dst 10 4419 ip-src ::1 ip-dst ::2222 eth-src 11:11:11:11:11:11 4420 eth-dst 22:22:22:22:22:22 4421 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4422 mplsoudp_encap / end 4423 4424IPv6 MPLSoUDP with VLAN outer header:: 4425 4426 testpmd> set mplsoudp_encap-with-vlan ip-version ipv6 mask 4 udp-src 5 4427 udp-dst 10 ip-src ::1 ip-dst ::2222 vlan-tci 34 4428 eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22 4429 testpmd> flow create 0 egress pattern eth / end actions l2_decap / 4430 mplsoudp_encap / end 4431 4432Sample MPLSoUDP decapsulation rule 4433~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4434 4435MPLSoUDP decapsulation outer layer has default value pre-configured in testpmd 4436source code, those can be changed by using the following commands 4437 4438IPv4 MPLSoUDP outer header:: 4439 4440 testpmd> set mplsoudp_decap ip-version ipv4 4441 testpmd> flow create 0 ingress pattern eth / ipv4 / udp / mpls / end actions 4442 mplsoudp_decap / l2_encap / end 4443 4444IPv4 MPLSoUDP with VLAN outer header:: 4445 4446 testpmd> set mplsoudp_decap-with-vlan ip-version ipv4 4447 testpmd> flow create 0 ingress pattern eth / vlan / ipv4 / udp / mpls / end 4448 actions mplsoudp_decap / l2_encap / end 4449 4450IPv6 MPLSoUDP outer header:: 4451 4452 testpmd> set mplsoudp_decap ip-version ipv6 4453 testpmd> flow create 0 ingress pattern eth / ipv6 / udp / mpls / end 4454 actions mplsoudp_decap / l2_encap / end 4455 4456IPv6 MPLSoUDP with VLAN outer header:: 4457 4458 testpmd> set mplsoudp_decap-with-vlan ip-version ipv6 4459 testpmd> flow create 0 ingress pattern eth / vlan / ipv6 / udp / mpls / end 4460 actions mplsoudp_decap / l2_encap / end 4461 4462BPF Functions 4463-------------- 4464 4465The following sections show functions to load/unload eBPF based filters. 4466 4467bpf-load 4468~~~~~~~~ 4469 4470Load an eBPF program as a callback for partciular RX/TX queue:: 4471 4472 testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename) 4473 4474The available load-flags are: 4475 4476* ``J``: use JIT generated native code, otherwise BPF interpreter will be used. 4477 4478* ``M``: assume input parameter is a pointer to rte_mbuf, otherwise assume it is a pointer to first segment's data. 4479 4480* ``-``: none. 4481 4482.. note:: 4483 4484 You'll need clang v3.7 or above to build bpf program you'd like to load 4485 4486For example: 4487 4488.. code-block:: console 4489 4490 cd test/bpf 4491 clang -O2 -target bpf -c t1.c 4492 4493Then to load (and JIT compile) t1.o at RX queue 0, port 1:: 4494 4495.. code-block:: console 4496 4497 testpmd> bpf-load rx 1 0 J ./dpdk.org/test/bpf/t1.o 4498 4499To load (not JITed) t1.o at TX queue 0, port 0:: 4500 4501.. code-block:: console 4502 4503 testpmd> bpf-load tx 0 0 - ./dpdk.org/test/bpf/t1.o 4504 4505bpf-unload 4506~~~~~~~~~~ 4507 4508Unload previously loaded eBPF program for partciular RX/TX queue:: 4509 4510 testpmd> bpf-unload rx|tx (portid) (queueid) 4511 4512For example to unload BPF filter from TX queue 0, port 0: 4513 4514.. code-block:: console 4515 4516 testpmd> bpf-load tx 0 0 - ./dpdk.org/test/bpf/t1.o 4517