On 3/6/2019 5:08 AM, Leon Romanovsky wrote:
From: Leon Romanovsky <leonro@xxxxxxxxxxxx>
Generalize the naming scheme for RDMA devices, so users will always
see names based on topology/GUID information. Such naming scheme has
big advantage that the names are fully automatic, fully predictable
and they stay fixed even if hardware is added or removed (i.e. no
reenumeration takes place) and that broken hardware can be replaced
seamlessly.
The naming policy is possible to chose from NAME_KERNEL, NAME_PCI,
NAME_GUID or NAME_FALLBACK, which is controlled by udev rule.
* NAME_KERNEL - don't change names and rely on kernel assignment. This
will keep RDMA names as before. Example: "mlx5_0".
* NAME_PCI - read PCI location and topology as a source for stable names,
which won't change in any software event (reset, PCI probe e.t.c.).
Example: "mlxp0s12f4".
* NAME_GUID - read system image GUID information in simillar manner to
net MAC naming policy. Example "mlxx525400c0fe123455".
* NAME_FALLBACK - automatic fallback: NAME_PCI->NAME_GUID->NAME_KERNEL
No doubts that new names are harder to read than the "mlx5_0" everybody,
is used to, but being consistent in scripts is much more important.
As a matter of precaution, we set default naming policy to be
NAME_KERNEL, but will change it later to NAME_FALLBACK.
What is the time frame for changing the default?
--Denny
