The Linux Kernel
4.18.0
  • Linux kernel licensing rules
  • The Linux kernel user’s and administrator’s guide
  • The Linux kernel user-space API guide
  • Working with the kernel development community
  • Development tools for the kernel
  • How to write kernel documentation
  • Kernel Hacking Guides
  • Linux Tracing Technologies
  • Kernel Maintainer Handbook
  • The Linux driver implementer’s API guide
  • Core API Documentation
  • InfiniBand
  • Linux Media Subsystem Documentation
  • Linux Networking Documentation
  • The Linux Input Documentation
  • Linux GPU Driver Developer’s Guide
  • Security Documentation
  • Linux Sound Subsystem Documentation
  • Linux Kernel Crypto API
  • Linux Filesystems API
  • Linux Memory Management Documentation
  • BPF Documentation
  • Linux PCI Bus Subsystem
  • Assembler Annotations
  • SuperH Interfaces Guide
  • x86 architecture specifics
  • Korean translations
  • Chinese translations
  • Japanese translations
The Linux Kernel
  • Docs »
  • mlxsw devlink support
  • View page source

mlxsw devlink support¶

This document describes the devlink features implemented by the mlxsw device driver.

Parameters¶

Generic parameters implemented¶
Name Mode
fw_load_policy driverinit

The mlxsw driver also implements the following driver-specific parameters.

Driver-specific parameters implemented¶
Name Type Mode Description
acl_region_rehash_interval u32 runtime Sets an interval for periodic ACL region rehashes. The value is specified in milliseconds, with a minimum of 3000. The value of 0 disables periodic work entirely. The first rehash will be run immediately after the value is set.

The mlxsw driver supports reloading via DEVLINK_CMD_RELOAD

Info versions¶

The mlxsw driver reports the following versions

devlink info versions implemented¶
Name Type Description
hw.revision fixed The hardware revision for this board
fw.psid fixed Firmware PSID
fw.version running Three digit firmware version

Driver-specific Traps¶

List of Driver-specific Traps Registered by mlxsw¶
Name Type Description
irif_disabled drop Traps packets that the device decided to drop because they need to be routed from a disabled router interface (RIF). This can happen during RIF dismantle, when the RIF is first disabled before being removed completely
erif_disabled drop Traps packets that the device decided to drop because they need to be routed through a disabled router interface (RIF). This can happen during RIF dismantle, when the RIF is first disabled before being removed completely

© Copyright The kernel development community.

Built with Sphinx using a theme provided by Read the Docs.