Loading...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 | .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB ================================================= Mellanox ConnectX(R) mlx5 core VPI Network Driver ================================================= Copyright (c) 2019, Mellanox Technologies LTD. Contents ======== - `Enabling the driver and kconfig options`_ - `Devlink info`_ - `Devlink parameters`_ - `Bridge offload`_ - `mlx5 subfunction`_ - `mlx5 function attributes`_ - `Devlink health reporters`_ - `mlx5 tracepoints`_ Enabling the driver and kconfig options ======================================= | mlx5 core is modular and most of the major mlx5 core driver features can be selected (compiled in/out) | at build time via kernel Kconfig flags. | Basic features, ethernet net device rx/tx offloads and XDP, are available with the most basic flags | CONFIG_MLX5_CORE=y/m and CONFIG_MLX5_CORE_EN=y. | For the list of advanced features, please see below. **CONFIG_MLX5_CORE=(y/m/n)** (module mlx5_core.ko) | The driver can be enabled by choosing CONFIG_MLX5_CORE=y/m in kernel config. | This will provide mlx5 core driver for mlx5 ulps to interface with (mlx5e, mlx5_ib). **CONFIG_MLX5_CORE_EN=(y/n)** | Choosing this option will allow basic ethernet netdevice support with all of the standard rx/tx offloads. | mlx5e is the mlx5 ulp driver which provides netdevice kernel interface, when chosen, mlx5e will be | built-in into mlx5_core.ko. **CONFIG_MLX5_EN_ARFS=(y/n)** | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering. | https://community.mellanox.com/s/article/howto-configure-arfs-on-connectx-4 **CONFIG_MLX5_EN_RXNFC=(y/n)** | Enables ethtool receive network flow classification, which allows user defined | flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc API. **CONFIG_MLX5_CORE_EN_DCB=(y/n)**: | Enables `Data Center Bridging (DCB) Support <https://community.mellanox.com/s/article/howto-auto-config-pfc-and-ets-on-connectx-4-via-lldp-dcbx>`_. **CONFIG_MLX5_MPFS=(y/n)** | Ethernet Multi-Physical Function Switch (MPFS) support in ConnectX NIC. | MPFs is required for when `Multi-Host <http://www.mellanox.com/page/multihost>`_ configuration is enabled to allow passing | user configured unicast MAC addresses to the requesting PF. **CONFIG_MLX5_ESWITCH=(y/n)** | Ethernet SRIOV E-Switch support in ConnectX NIC. E-Switch provides internal SRIOV packet steering | and switching for the enabled VFs and PF in two available modes: | 1) `Legacy SRIOV mode (L2 mac vlan steering based) <https://community.mellanox.com/s/article/howto-configure-sr-iov-for-connectx-4-connectx-5-with-kvm--ethernet-x>`_. | 2) `Switchdev mode (eswitch offloads) <https://www.mellanox.com/related-docs/prod_software/ASAP2_Hardware_Offloading_for_vSwitches_User_Manual_v4.4.pdf>`_. **CONFIG_MLX5_CORE_IPOIB=(y/n)** | IPoIB offloads & acceleration support. | Requires CONFIG_MLX5_CORE_EN to provide an accelerated interface for the rdma | IPoIB ulp netdevice. **CONFIG_MLX5_FPGA=(y/n)** | Build support for the Innova family of network cards by Mellanox Technologies. | Innova network cards are comprised of a ConnectX chip and an FPGA chip on one board. | If you select this option, the mlx5_core driver will include the Innova FPGA core and allow | building sandbox-specific client drivers. **CONFIG_MLX5_EN_IPSEC=(y/n)** | Enables `IPSec XFRM cryptography-offload acceleration <http://www.mellanox.com/related-docs/prod_software/Mellanox_Innova_IPsec_Ethernet_Adapter_Card_User_Manual.pdf>`_. **CONFIG_MLX5_EN_TLS=(y/n)** | TLS cryptography-offload acceleration. **CONFIG_MLX5_INFINIBAND=(y/n/m)** (module mlx5_ib.ko) | Provides low-level InfiniBand/RDMA and `RoCE <https://community.mellanox.com/s/article/recommended-network-configuration-examples-for-roce-deployment>`_ support. **CONFIG_MLX5_SF=(y/n)** | Build support for subfunction. | Subfunctons are more light weight than PCI SRIOV VFs. Choosing this option | will enable support for creating subfunction devices. **External options** ( Choose if the corresponding mlx5 feature is required ) - CONFIG_PTP_1588_CLOCK: When chosen, mlx5 ptp support will be enabled - CONFIG_VXLAN: When chosen, mlx5 vxlan support will be enabled. - CONFIG_MLXFW: When chosen, mlx5 firmware flashing support will be enabled (via devlink and ethtool). Devlink info ============ The devlink info reports the running and stored firmware versions on device. It also prints the device PSID which represents the HCA board type ID. User command example:: $ devlink dev info pci/0000:00:06.0 pci/0000:00:06.0: driver mlx5_core versions: fixed: fw.psid MT_0000000009 running: fw.version 16.26.0100 stored: fw.version 16.26.0100 Devlink parameters ================== flow_steering_mode: Device flow steering mode --------------------------------------------- The flow steering mode parameter controls the flow steering mode of the driver. Two modes are supported: 1. 'dmfs' - Device managed flow steering. 2. 'smfs' - Software/Driver managed flow steering. In DMFS mode, the HW steering entities are created and managed through the Firmware. In SMFS mode, the HW steering entities are created and managed though by the driver directly into hardware without firmware intervention. SMFS mode is faster and provides better rule insertion rate compared to default DMFS mode. User command examples: - Set SMFS flow steering mode:: $ devlink dev param set pci/0000:06:00.0 name flow_steering_mode value "smfs" cmode runtime - Read device flow steering mode:: $ devlink dev param show pci/0000:06:00.0 name flow_steering_mode pci/0000:06:00.0: name flow_steering_mode type driver-specific values: cmode runtime value smfs enable_roce: RoCE enablement state ---------------------------------- RoCE enablement state controls driver support for RoCE traffic. When RoCE is disabled, there is no gid table, only raw ethernet QPs are supported and traffic on the well-known UDP RoCE port is handled as raw ethernet traffic. To change RoCE enablement state, a user must change the driverinit cmode value and run devlink reload. User command examples: - Disable RoCE:: $ devlink dev param set pci/0000:06:00.0 name enable_roce value false cmode driverinit $ devlink dev reload pci/0000:06:00.0 - Read RoCE enablement state:: $ devlink dev param show pci/0000:06:00.0 name enable_roce pci/0000:06:00.0: name enable_roce type generic values: cmode driverinit value true esw_port_metadata: Eswitch port metadata state ---------------------------------------------- When applicable, disabling eswitch metadata can increase packet rate up to 20% depending on the use case and packet sizes. Eswitch port metadata state controls whether to internally tag packets with metadata. Metadata tagging must be enabled for multi-port RoCE, failover between representors and stacked devices. By default metadata is enabled on the supported devices in E-switch. Metadata is applicable only for E-switch in switchdev mode and users may disable it when NONE of the below use cases will be in use: 1. HCA is in Dual/multi-port RoCE mode. 2. VF/SF representor bonding (Usually used for Live migration) 3. Stacked devices When metadata is disabled, the above use cases will fail to initialize if users try to enable them. - Show eswitch port metadata:: $ devlink dev param show pci/0000:06:00.0 name esw_port_metadata pci/0000:06:00.0: name esw_port_metadata type driver-specific values: cmode runtime value true - Disable eswitch port metadata:: $ devlink dev param set pci/0000:06:00.0 name esw_port_metadata value false cmode runtime - Change eswitch mode to switchdev mode where after choosing the metadata value:: $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev Bridge offload ============== The mlx5 driver implements support for offloading bridge rules when in switchdev mode. Linux bridge FDBs are automatically offloaded when mlx5 switchdev representor is attached to bridge. - Change device to switchdev mode:: $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev - Attach mlx5 switchdev representor 'enp8s0f0' to bridge netdev 'bridge1':: $ ip link set enp8s0f0 master bridge1 VLANs ----- Following bridge VLAN functions are supported by mlx5: - VLAN filtering (including multiple VLANs per port):: $ ip link set bridge1 type bridge vlan_filtering 1 $ bridge vlan add dev enp8s0f0 vid 2-3 - VLAN push on bridge ingress:: $ bridge vlan add dev enp8s0f0 vid 3 pvid - VLAN pop on bridge egress:: $ bridge vlan add dev enp8s0f0 vid 3 untagged mlx5 subfunction ================ mlx5 supports subfunction management using devlink port (see :ref:`Documentation/networking/devlink/devlink-port.rst <devlink_port>`) interface. A subfunction has its own function capabilities and its own resources. This means a subfunction has its own dedicated queues (txq, rxq, cq, eq). These queues are neither shared nor stolen from the parent PCI function. When a subfunction is RDMA capable, it has its own QP1, GID table, and RDMA resources neither shared nor stolen from the parent PCI function. A subfunction has a dedicated window in PCI BAR space that is not shared with the other subfunctions or the parent PCI function. This ensures that all devices (netdev, rdma, vdpa, etc.) of the subfunction accesses only assigned PCI BAR space. A subfunction supports eswitch representation through which it supports tc offloads. The user configures eswitch to send/receive packets from/to the subfunction port. Subfunctions share PCI level resources such as PCI MSI-X IRQs with other subfunctions and/or with its parent PCI function. Example mlx5 software, system, and device view:: _______ | admin | | user |---------- |_______| | | | ____|____ __|______ _________________ | | | | | | | devlink | | tc tool | | user | | tool | |_________| | applications | |_________| | |_________________| | | | | | | | | Userspace +---------|-------------|-------------------|----------|--------------------+ | | +----------+ +----------+ Kernel | | | netdev | | rdma dev | | | +----------+ +----------+ (devlink port add/del | ^ ^ port function set) | | | | | +---------------| _____|___ | | _______|_______ | | | | | mlx5 class | | devlink | +------------+ | | drivers | | kernel | | rep netdev | | |(mlx5_core,ib) | |_________| +------------+ | |_______________| | | | ^ (devlink ops) | | (probe/remove) _________|________ | | ____|________ | subfunction | | +---------------+ | subfunction | | management driver|----- | subfunction |---| driver | | (mlx5_core) | | auxiliary dev | | (mlx5_core) | |__________________| +---------------+ |_____________| | ^ (sf add/del, vhca events) | | (device add/del) _____|____ ____|________ | | | subfunction | | PCI NIC |--- activate/deactivate events--->| host driver | |__________| | (mlx5_core) | |_____________| Subfunction is created using devlink port interface. - Change device to switchdev mode:: $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev - Add a devlink port of subfunction flavour:: $ devlink port add pci/0000:06:00.0 flavour pcisf pfnum 0 sfnum 88 pci/0000:06:00.0/32768: type eth netdev eth6 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false function: hw_addr 00:00:00:00:00:00 state inactive opstate detached - Show a devlink port of the subfunction:: $ devlink port show pci/0000:06:00.0/32768 pci/0000:06:00.0/32768: type eth netdev enp6s0pf0sf88 flavour pcisf pfnum 0 sfnum 88 function: hw_addr 00:00:00:00:00:00 state inactive opstate detached - Delete a devlink port of subfunction after use:: $ devlink port del pci/0000:06:00.0/32768 mlx5 function attributes ======================== The mlx5 driver provides a mechanism to setup PCI VF/SF function attributes in a unified way for SmartNIC and non-SmartNIC. This is supported only when the eswitch mode is set to switchdev. Port function configuration of the PCI VF/SF is supported through devlink eswitch port. Port function attributes should be set before PCI VF/SF is enumerated by the driver. MAC address setup ----------------- mlx5 driver support devlink port function attr mechanism to setup MAC address. (refer to Documentation/networking/devlink/devlink-port.rst) RoCE capability setup --------------------- Not all mlx5 PCI devices/SFs require RoCE capability. When RoCE capability is disabled, it saves 1 Mbytes worth of system memory per PCI devices/SF. mlx5 driver support devlink port function attr mechanism to setup RoCE capability. (refer to Documentation/networking/devlink/devlink-port.rst) migratable capability setup --------------------------- User who wants mlx5 PCI VFs to be able to perform live migration need to explicitly enable the VF migratable capability. mlx5 driver support devlink port function attr mechanism to setup migratable capability. (refer to Documentation/networking/devlink/devlink-port.rst) SF state setup -------------- To use the SF, the user must activate the SF using the SF function state attribute. - Get the state of the SF identified by its unique devlink port index:: $ devlink port show ens2f0npf0sf88 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false function: hw_addr 00:00:00:00:88:88 state inactive opstate detached - Activate the function and verify its state is active:: $ devlink port function set ens2f0npf0sf88 state active $ devlink port show ens2f0npf0sf88 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false function: hw_addr 00:00:00:00:88:88 state active opstate detached Upon function activation, the PF driver instance gets the event from the device that a particular SF was activated. It's the cue to put the device on bus, probe it and instantiate the devlink instance and class specific auxiliary devices for it. - Show the auxiliary device and port of the subfunction:: $ devlink dev show devlink dev show auxiliary/mlx5_core.sf.4 $ devlink port show auxiliary/mlx5_core.sf.4/1 auxiliary/mlx5_core.sf.4/1: type eth netdev p0sf88 flavour virtual port 0 splittable false $ rdma link show mlx5_0/1 link mlx5_0/1 state ACTIVE physical_state LINK_UP netdev p0sf88 $ rdma dev show 8: rocep6s0f1: node_type ca fw 16.29.0550 node_guid 248a:0703:00b3:d113 sys_image_guid 248a:0703:00b3:d112 13: mlx5_0: node_type ca fw 16.29.0550 node_guid 0000:00ff:fe00:8888 sys_image_guid 248a:0703:00b3:d112 - Subfunction auxiliary device and class device hierarchy:: mlx5_core.sf.4 (subfunction auxiliary device) /\ / \ / \ / \ / \ mlx5_core.eth.4 mlx5_core.rdma.4 (sf eth aux dev) (sf rdma aux dev) | | | | p0sf88 mlx5_0 (sf netdev) (sf rdma device) Additionally, the SF port also gets the event when the driver attaches to the auxiliary device of the subfunction. This results in changing the operational state of the function. This provides visibility to the user to decide when is it safe to delete the SF port for graceful termination of the subfunction. - Show the SF port operational state:: $ devlink port show ens2f0npf0sf88 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false function: hw_addr 00:00:00:00:88:88 state active opstate attached Devlink health reporters ======================== tx reporter ----------- The tx reporter is responsible for reporting and recovering of the following two error scenarios: - tx timeout Report on kernel tx timeout detection. Recover by searching lost interrupts. - tx error completion Report on error tx completion. Recover by flushing the tx queue and reset it. tx reporter also support on demand diagnose callback, on which it provides real time information of its send queues status. User commands examples: - Diagnose send queues status:: $ devlink health diagnose pci/0000:82:00.0 reporter tx NOTE: This command has valid output only when interface is up, otherwise the command has empty output. - Show number of tx errors indicated, number of recover flows ended successfully, is autorecover enabled and graceful period from last recover:: $ devlink health show pci/0000:82:00.0 reporter tx rx reporter ----------- The rx reporter is responsible for reporting and recovering of the following two error scenarios: - rx queues' initialization (population) timeout Population of rx queues' descriptors on ring initialization is done in napi context via triggering an irq. In case of a failure to get the minimum amount of descriptors, a timeout would occur, and descriptors could be recovered by polling the EQ (Event Queue). - rx completions with errors (reported by HW on interrupt context) Report on rx completion error. Recover (if needed) by flushing the related queue and reset it. rx reporter also supports on demand diagnose callback, on which it provides real time information of its receive queues' status. - Diagnose rx queues' status and corresponding completion queue:: $ devlink health diagnose pci/0000:82:00.0 reporter rx NOTE: This command has valid output only when interface is up. Otherwise, the command has empty output. - Show number of rx errors indicated, number of recover flows ended successfully, is autorecover enabled, and graceful period from last recover:: $ devlink health show pci/0000:82:00.0 reporter rx fw reporter ----------- The fw reporter implements `diagnose` and `dump` callbacks. It follows symptoms of fw error such as fw syndrome by triggering fw core dump and storing it into the dump buffer. The fw reporter diagnose command can be triggered any time by the user to check current fw status. User commands examples: - Check fw heath status:: $ devlink health diagnose pci/0000:82:00.0 reporter fw - Read FW core dump if already stored or trigger new one:: $ devlink health dump show pci/0000:82:00.0 reporter fw NOTE: This command can run only on the PF which has fw tracer ownership, running it on other PF or any VF will return "Operation not permitted". fw fatal reporter ----------------- The fw fatal reporter implements `dump` and `recover` callbacks. It follows fatal errors indications by CR-space dump and recover flow. The CR-space dump uses vsc interface which is valid even if the FW command interface is not functional, which is the case in most FW fatal errors. The recover function runs recover flow which reloads the driver and triggers fw reset if needed. On firmware error, the health buffer is dumped into the dmesg. The log level is derived from the error's severity (given in health buffer). User commands examples: - Run fw recover flow manually:: $ devlink health recover pci/0000:82:00.0 reporter fw_fatal - Read FW CR-space dump if already stored or trigger new one:: $ devlink health dump show pci/0000:82:00.1 reporter fw_fatal NOTE: This command can run only on PF. mlx5 tracepoints ================ mlx5 driver provides internal tracepoints for tracking and debugging using kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst). For the list of support mlx5 events, check `/sys/kernel/debug/tracing/events/mlx5/`. tc and eswitch offloads tracepoints: - mlx5e_configure_flower: trace flower filter actions and cookies offloaded to mlx5:: $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... tc-6535 [019] ...1 2672.404466: mlx5e_configure_flower: cookie=0000000067874a55 actions= REDIRECT - mlx5e_delete_flower: trace flower filter actions and cookies deleted from mlx5:: $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... tc-6569 [010] .N.1 2686.379075: mlx5e_delete_flower: cookie=0000000067874a55 actions= NULL - mlx5e_stats_flower: trace flower stats request:: $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... tc-6546 [010] ...1 2679.704889: mlx5e_stats_flower: cookie=0000000060eb3d6a bytes=0 packets=0 lastused=4295560217 - mlx5e_tc_update_neigh_used_value: trace tunnel rule neigh update value offloaded to mlx5:: $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u48:4-8806 [009] ...1 55117.882428: mlx5e_tc_update_neigh_used_value: netdev: ens1f0 IPv4: 1.1.1.10 IPv6: ::ffff:1.1.1.10 neigh_used=1 - mlx5e_rep_neigh_update: trace neigh update tasks scheduled due to neigh state change events:: $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u48:7-2221 [009] ...1 1475.387435: mlx5e_rep_neigh_update: netdev: ens1f0 MAC: 24:8a:07:9a:17:9a IPv4: 1.1.1.10 IPv6: ::ffff:1.1.1.10 neigh_connected=1 Bridge offloads tracepoints: - mlx5_esw_bridge_fdb_entry_init: trace bridge FDB entry offloaded to mlx5:: $ echo mlx5:mlx5_esw_bridge_fdb_entry_init >> set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u20:9-2217 [003] ...1 318.582243: mlx5_esw_bridge_fdb_entry_init: net_device=enp8s0f0_0 addr=e4:fd:05:08:00:02 vid=0 flags=0 used=0 - mlx5_esw_bridge_fdb_entry_cleanup: trace bridge FDB entry deleted from mlx5:: $ echo mlx5:mlx5_esw_bridge_fdb_entry_cleanup >> set_event $ cat /sys/kernel/debug/tracing/trace ... ip-2581 [005] ...1 318.629871: mlx5_esw_bridge_fdb_entry_cleanup: net_device=enp8s0f0_1 addr=e4:fd:05:08:00:03 vid=0 flags=0 used=16 - mlx5_esw_bridge_fdb_entry_refresh: trace bridge FDB entry offload refreshed in mlx5:: $ echo mlx5:mlx5_esw_bridge_fdb_entry_refresh >> set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u20:8-3849 [003] ...1 466716: mlx5_esw_bridge_fdb_entry_refresh: net_device=enp8s0f0_0 addr=e4:fd:05:08:00:02 vid=3 flags=0 used=0 - mlx5_esw_bridge_vlan_create: trace bridge VLAN object add on mlx5 representor:: $ echo mlx5:mlx5_esw_bridge_vlan_create >> set_event $ cat /sys/kernel/debug/tracing/trace ... ip-2560 [007] ...1 318.460258: mlx5_esw_bridge_vlan_create: vid=1 flags=6 - mlx5_esw_bridge_vlan_cleanup: trace bridge VLAN object delete from mlx5 representor:: $ echo mlx5:mlx5_esw_bridge_vlan_cleanup >> set_event $ cat /sys/kernel/debug/tracing/trace ... bridge-2582 [007] ...1 318.653496: mlx5_esw_bridge_vlan_cleanup: vid=2 flags=8 - mlx5_esw_bridge_vport_init: trace mlx5 vport assigned with bridge upper device:: $ echo mlx5:mlx5_esw_bridge_vport_init >> set_event $ cat /sys/kernel/debug/tracing/trace ... ip-2560 [007] ...1 318.458915: mlx5_esw_bridge_vport_init: vport_num=1 - mlx5_esw_bridge_vport_cleanup: trace mlx5 vport removed from bridge upper device:: $ echo mlx5:mlx5_esw_bridge_vport_cleanup >> set_event $ cat /sys/kernel/debug/tracing/trace ... ip-5387 [000] ...1 573713: mlx5_esw_bridge_vport_cleanup: vport_num=1 Eswitch QoS tracepoints: - mlx5_esw_vport_qos_create: trace creation of transmit scheduler arbiter for vport:: $ echo mlx5:mlx5_esw_vport_qos_create >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-23496 [018] .... 73136.838831: mlx5_esw_vport_qos_create: (0000:82:00.0) vport=2 tsar_ix=4 bw_share=0, max_rate=0 group=000000007b576bb3 - mlx5_esw_vport_qos_config: trace configuration of transmit scheduler arbiter for vport:: $ echo mlx5:mlx5_esw_vport_qos_config >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-26548 [023] .... 75754.223823: mlx5_esw_vport_qos_config: (0000:82:00.0) vport=1 tsar_ix=3 bw_share=34, max_rate=10000 group=000000007b576bb3 - mlx5_esw_vport_qos_destroy: trace deletion of transmit scheduler arbiter for vport:: $ echo mlx5:mlx5_esw_vport_qos_destroy >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-27418 [004] .... 76546.680901: mlx5_esw_vport_qos_destroy: (0000:82:00.0) vport=1 tsar_ix=3 - mlx5_esw_group_qos_create: trace creation of transmit scheduler arbiter for rate group:: $ echo mlx5:mlx5_esw_group_qos_create >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-26578 [008] .... 75776.022112: mlx5_esw_group_qos_create: (0000:82:00.0) group=000000008dac63ea tsar_ix=5 - mlx5_esw_group_qos_config: trace configuration of transmit scheduler arbiter for rate group:: $ echo mlx5:mlx5_esw_group_qos_config >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-27303 [020] .... 76461.455356: mlx5_esw_group_qos_config: (0000:82:00.0) group=000000008dac63ea tsar_ix=5 bw_share=100 max_rate=20000 - mlx5_esw_group_qos_destroy: trace deletion of transmit scheduler arbiter for group:: $ echo mlx5:mlx5_esw_group_qos_destroy >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... <...>-27418 [006] .... 76547.187258: mlx5_esw_group_qos_destroy: (0000:82:00.0) group=000000007b576bb3 tsar_ix=1 SF tracepoints: - mlx5_sf_add: trace addition of the SF port:: $ echo mlx5:mlx5_sf_add >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... devlink-9363 [031] ..... 24610.188722: mlx5_sf_add: (0000:06:00.0) port_index=32768 controller=0 hw_id=0x8000 sfnum=88 - mlx5_sf_free: trace freeing of the SF port:: $ echo mlx5:mlx5_sf_free >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... devlink-9830 [038] ..... 26300.404749: mlx5_sf_free: (0000:06:00.0) port_index=32768 controller=0 hw_id=0x8000 - mlx5_sf_hwc_alloc: trace allocating of the hardware SF context:: $ echo mlx5:mlx5_sf_hwc_alloc >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... devlink-9775 [031] ..... 26296.385259: mlx5_sf_hwc_alloc: (0000:06:00.0) controller=0 hw_id=0x8000 sfnum=88 - mlx5_sf_hwc_free: trace freeing of the hardware SF context:: $ echo mlx5:mlx5_sf_hwc_free >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u128:3-9093 [046] ..... 24625.365771: mlx5_sf_hwc_free: (0000:06:00.0) hw_id=0x8000 - mlx5_sf_hwc_deferred_free : trace deferred freeing of the hardware SF context:: $ echo mlx5:mlx5_sf_hwc_deferred_free >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... devlink-9519 [046] ..... 24624.400271: mlx5_sf_hwc_deferred_free: (0000:06:00.0) hw_id=0x8000 - mlx5_sf_vhca_event: trace SF vhca event and state:: $ echo mlx5:mlx5_sf_vhca_event >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u128:3-9093 [046] ..... 24625.365525: mlx5_sf_vhca_event: (0000:06:00.0) hw_id=0x8000 sfnum=88 vhca_state=1 - mlx5_sf_dev_add : trace SF device add event:: $ echo mlx5:mlx5_sf_dev_add>> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u128:3-9093 [000] ..... 24616.524495: mlx5_sf_dev_add: (0000:06:00.0) sfdev=00000000fc5d96fd aux_id=4 hw_id=0x8000 sfnum=88 - mlx5_sf_dev_del : trace SF device delete event:: $ echo mlx5:mlx5_sf_dev_del >> /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace ... kworker/u128:3-9093 [044] ..... 24624.400749: mlx5_sf_dev_del: (0000:06:00.0) sfdev=00000000fc5d96fd aux_id=4 hw_id=0x8000 sfnum=88 |