1 .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
3 =================================================
4 Mellanox ConnectX(R) mlx5 core VPI Network Driver
5 =================================================
7 Copyright (c) 2019, Mellanox Technologies LTD.
12 - `Enabling the driver and kconfig options`_
14 - `Devlink parameters`_
17 - `mlx5 function attributes`_
18 - `Devlink health reporters`_
21 Enabling the driver and kconfig options
22 =======================================
24 | mlx5 core is modular and most of the major mlx5 core driver features can be selected (compiled in/out)
25 | at build time via kernel Kconfig flags.
26 | Basic features, ethernet net device rx/tx offloads and XDP, are available with the most basic flags
27 | CONFIG_MLX5_CORE=y/m and CONFIG_MLX5_CORE_EN=y.
28 | For the list of advanced features please see below.
30 **CONFIG_MLX5_CORE=(y/m/n)** (module mlx5_core.ko)
32 | The driver can be enabled by choosing CONFIG_MLX5_CORE=y/m in kernel config.
33 | This will provide mlx5 core driver for mlx5 ulps to interface with (mlx5e, mlx5_ib).
36 **CONFIG_MLX5_CORE_EN=(y/n)**
38 | Choosing this option will allow basic ethernet netdevice support with all of the standard rx/tx offloads.
39 | mlx5e is the mlx5 ulp driver which provides netdevice kernel interface, when chosen, mlx5e will be
40 | built-in into mlx5_core.ko.
43 **CONFIG_MLX5_EN_ARFS=(y/n)**
45 | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering.
46 | https://community.mellanox.com/s/article/howto-configure-arfs-on-connectx-4
49 **CONFIG_MLX5_EN_RXNFC=(y/n)**
51 | Enables ethtool receive network flow classification, which allows user defined
52 | flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc API.
55 **CONFIG_MLX5_CORE_EN_DCB=(y/n)**:
57 | Enables `Data Center Bridging (DCB) Support <https://community.mellanox.com/s/article/howto-auto-config-pfc-and-ets-on-connectx-4-via-lldp-dcbx>`_.
60 **CONFIG_MLX5_MPFS=(y/n)**
62 | Ethernet Multi-Physical Function Switch (MPFS) support in ConnectX NIC.
63 | MPFs is required for when `Multi-Host <http://www.mellanox.com/page/multihost>`_ configuration is enabled to allow passing
64 | user configured unicast MAC addresses to the requesting PF.
67 **CONFIG_MLX5_ESWITCH=(y/n)**
69 | Ethernet SRIOV E-Switch support in ConnectX NIC. E-Switch provides internal SRIOV packet steering
70 | and switching for the enabled VFs and PF in two available modes:
71 | 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>`_.
72 | 2) `Switchdev mode (eswitch offloads) <https://www.mellanox.com/related-docs/prod_software/ASAP2_Hardware_Offloading_for_vSwitches_User_Manual_v4.4.pdf>`_.
75 **CONFIG_MLX5_CORE_IPOIB=(y/n)**
77 | IPoIB offloads & acceleration support.
78 | Requires CONFIG_MLX5_CORE_EN to provide an accelerated interface for the rdma
79 | IPoIB ulp netdevice.
82 **CONFIG_MLX5_FPGA=(y/n)**
84 | Build support for the Innova family of network cards by Mellanox Technologies.
85 | Innova network cards are comprised of a ConnectX chip and an FPGA chip on one board.
86 | If you select this option, the mlx5_core driver will include the Innova FPGA core and allow
87 | building sandbox-specific client drivers.
90 **CONFIG_MLX5_EN_IPSEC=(y/n)**
92 | Enables `IPSec XFRM cryptography-offload accelaration <http://www.mellanox.com/related-docs/prod_software/Mellanox_Innova_IPsec_Ethernet_Adapter_Card_User_Manual.pdf>`_.
94 **CONFIG_MLX5_EN_TLS=(y/n)**
96 | TLS cryptography-offload accelaration.
99 **CONFIG_MLX5_INFINIBAND=(y/n/m)** (module mlx5_ib.ko)
101 | Provides low-level InfiniBand/RDMA and `RoCE <https://community.mellanox.com/s/article/recommended-network-configuration-examples-for-roce-deployment>`_ support.
103 **CONFIG_MLX5_SF=(y/n)**
105 | Build support for subfunction.
106 | Subfunctons are more light weight than PCI SRIOV VFs. Choosing this option
107 | will enable support for creating subfunction devices.
109 **External options** ( Choose if the corresponding mlx5 feature is required )
111 - CONFIG_PTP_1588_CLOCK: When chosen, mlx5 ptp support will be enabled
112 - CONFIG_VXLAN: When chosen, mlx5 vxlan support will be enabled.
113 - CONFIG_MLXFW: When chosen, mlx5 firmware flashing support will be enabled (via devlink and ethtool).
118 The devlink info reports the running and stored firmware versions on device.
119 It also prints the device PSID which represents the HCA board type ID.
121 User command example::
123 $ devlink dev info pci/0000:00:06.0
128 fw.psid MT_0000000009
130 fw.version 16.26.0100
132 fw.version 16.26.0100
137 flow_steering_mode: Device flow steering mode
138 ---------------------------------------------
139 The flow steering mode parameter controls the flow steering mode of the driver.
140 Two modes are supported:
141 1. 'dmfs' - Device managed flow steering.
142 2. 'smfs - Software/Driver managed flow steering.
144 In DMFS mode, the HW steering entities are created and managed through the
146 In SMFS mode, the HW steering entities are created and managed though by
147 the driver directly into Hardware without firmware intervention.
149 SMFS mode is faster and provides better rule inserstion rate compared to default DMFS mode.
151 User command examples:
153 - Set SMFS flow steering mode::
155 $ devlink dev param set pci/0000:06:00.0 name flow_steering_mode value "smfs" cmode runtime
157 - Read device flow steering mode::
159 $ devlink dev param show pci/0000:06:00.0 name flow_steering_mode
161 name flow_steering_mode type driver-specific
163 cmode runtime value smfs
165 enable_roce: RoCE enablement state
166 ----------------------------------
167 RoCE enablement state controls driver support for RoCE traffic.
168 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.
170 To change RoCE enablement state a user must change the driverinit cmode value and run devlink reload.
172 User command examples:
176 $ devlink dev param set pci/0000:06:00.0 name enable_roce value false cmode driverinit
177 $ devlink dev reload pci/0000:06:00.0
179 - Read RoCE enablement state::
181 $ devlink dev param show pci/0000:06:00.0 name enable_roce
183 name enable_roce type generic
185 cmode driverinit value true
187 esw_port_metadata: Eswitch port metadata state
188 ----------------------------------------------
189 When applicable, disabling Eswitch metadata can increase packet rate
190 up to 20% depending on the use case and packet sizes.
192 Eswitch port metadata state controls whether to internally tag packets with
193 metadata. Metadata tagging must be enabled for multi-port RoCE, failover
194 between representors and stacked devices.
195 By default metadata is enabled on the supported devices in E-switch.
196 Metadata is applicable only for E-switch in switchdev mode and
197 users may disable it when NONE of the below use cases will be in use:
198 1. HCA is in Dual/multi-port RoCE mode.
199 2. VF/SF representor bonding (Usually used for Live migration)
202 When metadata is disabled, the above use cases will fail to initialize if
203 users try to enable them.
205 - Show eswitch port metadata::
207 $ devlink dev param show pci/0000:06:00.0 name esw_port_metadata
209 name esw_port_metadata type driver-specific
211 cmode runtime value true
213 - Disable eswitch port metadata::
215 $ devlink dev param set pci/0000:06:00.0 name esw_port_metadata value false cmode runtime
217 - Change eswitch mode to switchdev mode where after choosing the metadata value::
219 $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev
223 The mlx5 driver implements support for offloading bridge rules when in switchdev
224 mode. Linux bridge FDBs are automatically offloaded when mlx5 switchdev
225 representor is attached to bridge.
227 - Change device to switchdev mode::
229 $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev
231 - Attach mlx5 switchdev representor 'enp8s0f0' to bridge netdev 'bridge1'::
233 $ ip link set enp8s0f0 master bridge1
237 Following bridge VLAN functions are supported by mlx5:
239 - VLAN filtering (including multiple VLANs per port)::
241 $ ip link set bridge1 type bridge vlan_filtering 1
242 $ bridge vlan add dev enp8s0f0 vid 2-3
244 - VLAN push on bridge ingress::
246 $ bridge vlan add dev enp8s0f0 vid 3 pvid
248 - VLAN pop on bridge egress::
250 $ bridge vlan add dev enp8s0f0 vid 3 untagged
254 mlx5 supports subfunction management using devlink port (see :ref:`Documentation/networking/devlink/devlink-port.rst <devlink_port>`) interface.
256 A Subfunction has its own function capabilities and its own resources. This
257 means a subfunction has its own dedicated queues (txq, rxq, cq, eq). These
258 queues are neither shared nor stolen from the parent PCI function.
260 When a subfunction is RDMA capable, it has its own QP1, GID table and rdma
261 resources neither shared nor stolen from the parent PCI function.
263 A subfunction has a dedicated window in PCI BAR space that is not shared
264 with ther other subfunctions or the parent PCI function. This ensures that all
265 devices (netdev, rdma, vdpa etc.) of the subfunction accesses only assigned
268 A Subfunction supports eswitch representation through which it supports tc
269 offloads. The user configures eswitch to send/receive packets from/to
270 the subfunction port.
272 Subfunctions share PCI level resources such as PCI MSI-X IRQs with
273 other subfunctions and/or with its parent PCI function.
275 Example mlx5 software, system and device view::
282 ____|____ __|______ _________________
284 | devlink | | tc tool | | user |
285 | tool | |_________| | applications |
286 |_________| | |_________________|
289 +---------|-------------|-------------------|----------|--------------------+
290 | | +----------+ +----------+ Kernel
291 | | | netdev | | rdma dev |
292 | | +----------+ +----------+
293 (devlink port add/del | ^ ^
294 port function set) | | |
295 | | +---------------|
296 _____|___ | | _______|_______
297 | | | | | mlx5 class |
298 | devlink | +------------+ | | drivers |
299 | kernel | | rep netdev | | |(mlx5_core,ib) |
300 |_________| +------------+ | |_______________|
302 (devlink ops) | | (probe/remove)
303 _________|________ | | ____|________
304 | subfunction | | +---------------+ | subfunction |
305 | management driver|----- | subfunction |---| driver |
306 | (mlx5_core) | | auxiliary dev | | (mlx5_core) |
307 |__________________| +---------------+ |_____________|
309 (sf add/del, vhca events) |
311 _____|____ ____|________
313 | PCI NIC |---- activate/deactive events---->| host driver |
314 |__________| | (mlx5_core) |
317 Subfunction is created using devlink port interface.
319 - Change device to switchdev mode::
321 $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev
323 - Add a devlink port of subfunction flaovur::
325 $ devlink port add pci/0000:06:00.0 flavour pcisf pfnum 0 sfnum 88
326 pci/0000:06:00.0/32768: type eth netdev eth6 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false
328 hw_addr 00:00:00:00:00:00 state inactive opstate detached
330 - Show a devlink port of the subfunction::
332 $ devlink port show pci/0000:06:00.0/32768
333 pci/0000:06:00.0/32768: type eth netdev enp6s0pf0sf88 flavour pcisf pfnum 0 sfnum 88
335 hw_addr 00:00:00:00:00:00 state inactive opstate detached
337 - Delete a devlink port of subfunction after use::
339 $ devlink port del pci/0000:06:00.0/32768
341 mlx5 function attributes
342 ========================
343 The mlx5 driver provides a mechanism to setup PCI VF/SF function attributes in
344 a unified way for SmartNIC and non-SmartNIC.
346 This is supported only when the eswitch mode is set to switchdev. Port function
347 configuration of the PCI VF/SF is supported through devlink eswitch port.
349 Port function attributes should be set before PCI VF/SF is enumerated by the
354 mlx5 driver provides mechanism to setup the MAC address of the PCI VF/SF.
356 The configured MAC address of the PCI VF/SF will be used by netdevice and rdma
357 device created for the PCI VF/SF.
359 - Get the MAC address of the VF identified by its unique devlink port index::
361 $ devlink port show pci/0000:06:00.0/2
362 pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0 vfnum 1
364 hw_addr 00:00:00:00:00:00
366 - Set the MAC address of the VF identified by its unique devlink port index::
368 $ devlink port function set pci/0000:06:00.0/2 hw_addr 00:11:22:33:44:55
370 $ devlink port show pci/0000:06:00.0/2
371 pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0 vfnum 1
373 hw_addr 00:11:22:33:44:55
375 - Get the MAC address of the SF identified by its unique devlink port index::
377 $ devlink port show pci/0000:06:00.0/32768
378 pci/0000:06:00.0/32768: type eth netdev enp6s0pf0sf88 flavour pcisf pfnum 0 sfnum 88
380 hw_addr 00:00:00:00:00:00
382 - Set the MAC address of the VF identified by its unique devlink port index::
384 $ devlink port function set pci/0000:06:00.0/32768 hw_addr 00:00:00:00:88:88
386 $ devlink port show pci/0000:06:00.0/32768
387 pci/0000:06:00.0/32768: type eth netdev enp6s0pf0sf88 flavour pcivf pfnum 0 sfnum 88
389 hw_addr 00:00:00:00:88:88
393 To use the SF, the user must active the SF using the SF function state
396 - Get the state of the SF identified by its unique devlink port index::
398 $ devlink port show ens2f0npf0sf88
399 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false
401 hw_addr 00:00:00:00:88:88 state inactive opstate detached
403 - Activate the function and verify its state is active::
405 $ devlink port function set ens2f0npf0sf88 state active
407 $ devlink port show ens2f0npf0sf88
408 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false
410 hw_addr 00:00:00:00:88:88 state active opstate detached
412 Upon function activation, the PF driver instance gets the event from the device
413 that a particular SF was activated. It's the cue to put the device on bus, probe
414 it and instantiate the devlink instance and class specific auxiliary devices
417 - Show the auxiliary device and port of the subfunction::
420 devlink dev show auxiliary/mlx5_core.sf.4
422 $ devlink port show auxiliary/mlx5_core.sf.4/1
423 auxiliary/mlx5_core.sf.4/1: type eth netdev p0sf88 flavour virtual port 0 splittable false
425 $ rdma link show mlx5_0/1
426 link mlx5_0/1 state ACTIVE physical_state LINK_UP netdev p0sf88
429 8: rocep6s0f1: node_type ca fw 16.29.0550 node_guid 248a:0703:00b3:d113 sys_image_guid 248a:0703:00b3:d112
430 13: mlx5_0: node_type ca fw 16.29.0550 node_guid 0000:00ff:fe00:8888 sys_image_guid 248a:0703:00b3:d112
432 - Subfunction auxiliary device and class device hierarchy::
435 (subfunction auxiliary device)
441 mlx5_core.eth.4 mlx5_core.rdma.4
442 (sf eth aux dev) (sf rdma aux dev)
446 (sf netdev) (sf rdma device)
448 Additionally, the SF port also gets the event when the driver attaches to the
449 auxiliary device of the subfunction. This results in changing the operational
450 state of the function. This provides visiblity to the user to decide when is it
451 safe to delete the SF port for graceful termination of the subfunction.
453 - Show the SF port operational state::
455 $ devlink port show ens2f0npf0sf88
456 pci/0000:06:00.0/32768: type eth netdev ens2f0npf0sf88 flavour pcisf controller 0 pfnum 0 sfnum 88 external false splittable false
458 hw_addr 00:00:00:00:88:88 state active opstate attached
460 Devlink health reporters
461 ========================
465 The tx reporter is responsible for reporting and recovering of the following two error scenarios:
468 Report on kernel tx timeout detection.
469 Recover by searching lost interrupts.
470 - TX error completion
471 Report on error tx completion.
472 Recover by flushing the TX queue and reset it.
474 TX reporter also support on demand diagnose callback, on which it provides
475 real time information of its send queues status.
477 User commands examples:
479 - Diagnose send queues status::
481 $ devlink health diagnose pci/0000:82:00.0 reporter tx
483 NOTE: This command has valid output only when interface is up, otherwise the command has empty output.
485 - Show number of tx errors indicated, number of recover flows ended successfully,
486 is autorecover enabled and graceful period from last recover::
488 $ devlink health show pci/0000:82:00.0 reporter tx
492 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
494 - RX queues initialization (population) timeout
495 RX queues descriptors population on ring initialization is done in
496 napi context via triggering an irq, in case of a failure to get
497 the minimum amount of descriptors, a timeout would occur and it
498 could be recoverable by polling the EQ (Event Queue).
499 - RX completions with errors (reported by HW on interrupt context)
500 Report on rx completion error.
501 Recover (if needed) by flushing the related queue and reset it.
503 RX reporter also supports on demand diagnose callback, on which it
504 provides real time information of its receive queues status.
506 - Diagnose rx queues status, and corresponding completion queue::
508 $ devlink health diagnose pci/0000:82:00.0 reporter rx
510 NOTE: This command has valid output only when interface is up, otherwise the command has empty output.
512 - Show number of rx errors indicated, number of recover flows ended successfully,
513 is autorecover enabled and graceful period from last recover::
515 $ devlink health show pci/0000:82:00.0 reporter rx
519 The fw reporter implements diagnose and dump callbacks.
520 It follows symptoms of fw error such as fw syndrome by triggering
521 fw core dump and storing it into the dump buffer.
522 The fw reporter diagnose command can be triggered any time by the user to check
525 User commands examples:
527 - Check fw heath status::
529 $ devlink health diagnose pci/0000:82:00.0 reporter fw
531 - Read FW core dump if already stored or trigger new one::
533 $ devlink health dump show pci/0000:82:00.0 reporter fw
535 NOTE: This command can run only on the PF which has fw tracer ownership,
536 running it on other PF or any VF will return "Operation not permitted".
540 The fw fatal reporter implements dump and recover callbacks.
541 It follows fatal errors indications by CR-space dump and recover flow.
542 The CR-space dump uses vsc interface which is valid even if the FW command
543 interface is not functional, which is the case in most FW fatal errors.
544 The recover function runs recover flow which reloads the driver and triggers fw
547 User commands examples:
549 - Run fw recover flow manually::
551 $ devlink health recover pci/0000:82:00.0 reporter fw_fatal
553 - Read FW CR-space dump if already strored or trigger new one::
555 $ devlink health dump show pci/0000:82:00.1 reporter fw_fatal
557 NOTE: This command can run only on PF.
562 mlx5 driver provides internal trace points for tracking and debugging using
563 kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst).
565 For the list of support mlx5 events check /sys/kernel/debug/tracing/events/mlx5/
567 tc and eswitch offloads tracepoints:
569 - mlx5e_configure_flower: trace flower filter actions and cookies offloaded to mlx5::
571 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/debug/tracing/set_event
572 $ cat /sys/kernel/debug/tracing/trace
574 tc-6535 [019] ...1 2672.404466: mlx5e_configure_flower: cookie=0000000067874a55 actions= REDIRECT
576 - mlx5e_delete_flower: trace flower filter actions and cookies deleted from mlx5::
578 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/debug/tracing/set_event
579 $ cat /sys/kernel/debug/tracing/trace
581 tc-6569 [010] .N.1 2686.379075: mlx5e_delete_flower: cookie=0000000067874a55 actions= NULL
583 - mlx5e_stats_flower: trace flower stats request::
585 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/debug/tracing/set_event
586 $ cat /sys/kernel/debug/tracing/trace
588 tc-6546 [010] ...1 2679.704889: mlx5e_stats_flower: cookie=0000000060eb3d6a bytes=0 packets=0 lastused=4295560217
590 - mlx5e_tc_update_neigh_used_value: trace tunnel rule neigh update value offloaded to mlx5::
592 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/debug/tracing/set_event
593 $ cat /sys/kernel/debug/tracing/trace
595 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
597 - mlx5e_rep_neigh_update: trace neigh update tasks scheduled due to neigh state change events::
599 $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/debug/tracing/set_event
600 $ cat /sys/kernel/debug/tracing/trace
602 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
604 Bridge offloads tracepoints:
606 - mlx5_esw_bridge_fdb_entry_init: trace bridge FDB entry offloaded to mlx5::
608 $ echo mlx5:mlx5_esw_bridge_fdb_entry_init >> set_event
609 $ cat /sys/kernel/debug/tracing/trace
611 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
613 - mlx5_esw_bridge_fdb_entry_cleanup: trace bridge FDB entry deleted from mlx5::
615 $ echo mlx5:mlx5_esw_bridge_fdb_entry_cleanup >> set_event
616 $ cat /sys/kernel/debug/tracing/trace
618 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
620 - mlx5_esw_bridge_fdb_entry_refresh: trace bridge FDB entry offload refreshed in
623 $ echo mlx5:mlx5_esw_bridge_fdb_entry_refresh >> set_event
624 $ cat /sys/kernel/debug/tracing/trace
626 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
628 - mlx5_esw_bridge_vlan_create: trace bridge VLAN object add on mlx5
631 $ echo mlx5:mlx5_esw_bridge_vlan_create >> set_event
632 $ cat /sys/kernel/debug/tracing/trace
634 ip-2560 [007] ...1 318.460258: mlx5_esw_bridge_vlan_create: vid=1 flags=6
636 - mlx5_esw_bridge_vlan_cleanup: trace bridge VLAN object delete from mlx5
639 $ echo mlx5:mlx5_esw_bridge_vlan_cleanup >> set_event
640 $ cat /sys/kernel/debug/tracing/trace
642 bridge-2582 [007] ...1 318.653496: mlx5_esw_bridge_vlan_cleanup: vid=2 flags=8
644 - mlx5_esw_bridge_vport_init: trace mlx5 vport assigned with bridge upper
647 $ echo mlx5:mlx5_esw_bridge_vport_init >> set_event
648 $ cat /sys/kernel/debug/tracing/trace
650 ip-2560 [007] ...1 318.458915: mlx5_esw_bridge_vport_init: vport_num=1
652 - mlx5_esw_bridge_vport_cleanup: trace mlx5 vport removed from bridge upper
655 $ echo mlx5:mlx5_esw_bridge_vport_cleanup >> set_event
656 $ cat /sys/kernel/debug/tracing/trace
658 ip-5387 [000] ...1 573713: mlx5_esw_bridge_vport_cleanup: vport_num=1