User Manual

Rev 2.1-1.0.6
Mellanox Technologies
239
Appendix C: mlx4 Module Parameters
In order to set mlx4 parameters, add the following line(s) to /etc/modprobe.conf:
and/or
and/or
The following sections list the available
mlx4 parameters.
C.1 mlx4_ib Parameters
C.2 mlx4_core Parameters
options mlx4_core parameter=<value>
options mlx4_ib parameter=<value>
options mlx4_en parameter=<value>
sm_guid_assign: Enable SM alias_GUID assignment if sm_guid_assign > 0
(Default: 1) (int)
dev_assign_str
1
:
1. In the current version, this parameter is using decimal number to describe the InfiniBand device and
not hexadecimal number as it was in previous versions in order to uniform the mapping of device
function numbers to InfiniBand device numbers as defined for other module parameters (e.g. num_vfs
and probe_vf).
For example to map mlx4_15 to device function number 04:00.0 in the current version we use
“options mlx4_ib dev_assign_str=04:00.0-15” as opposed to the previous version in which we
used
“options mlx4_ib dev_assign_str=04:00.0-f”
Map device function numbers to IB device numbers
(e.g.'0000:04:00.0-0,002b:1c:0b.a-1,...').
Hexadecimal digits for the device function (e.g. 002b:1c:0b.a)
and decimal for IB device numbers (e.g. 1). Max supported
devices - 32 (string)
set_4k_mtu: (Obsolete) attempt to set 4K MTU to all ConnectX ports (int)
debug_level: Enable debug tracing if > 0 (int)
msi_x: 0 - don't use MSI-X,
1 - use MSI-X,
>1 - limit number of MSI-X irqs to msi_x (non-SRIOV only) (int)
enable_sys_tune: Tune the cpu's for better performance (default 0) (int)
block_loopback: Block multicast loopback packets if > 0 (default: 1) (int)
num_vfs: Either a single value (e.g. '5') to define uniform num_vfs
value for all devices functions or a string to map device func-
tion numbers to their num_vfs values (e.g. '0000:04:00.0-
5,002b:1c:0b.a-15').
Hexadecimal digits for the device function (e.g. 002b:1c:0b.a)
and decimal for num_vfs value (e.g. 15). (string)
probe_vf: Either a single value (e.g. '3') to indicate that the Hypervi-
sor driver itself should activate this number of VFs for each
HCA on the host, or a string to map device function numbers to
their probe_vf values (e.g. '0000:04:00.0-3,002b:1c:0b.a-13').
Hexadecimal digits for the device function (e.g. 002b:1c:0b.a)
and decimal for probe_vf value (e.g. 13). (string)