On Wed, 2018-10-10 at 09:19 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@xxxxxxxxxxxx>
>
> Changelog:
> v2 -> v3:
> * Fixed forgotten put_device after successful get_device.
> v1 -> v2:
> * Added update of ibdev->name to device rename routine
> v0 -> v1:
> * Based on Jason's latest dev_name changes
> * Dropped all patches related to alloc_name changes
>
> -----------------------------------------------------------------------
> Hi,
>
> This series introduce long-waiting feature - "IB device rename".
> Such feature gives and option to rename user visible IB device name from
> vendor specific name (e.g. mlx5_0) to anything else.
>
> The user space component through rdmatool was already sent to the ML.
>
> [leonro@server /]$ lspci |grep -i Ether
> 00:08.0 Ethernet controller: Red Hat, Inc. Virtio network device
> 00:09.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]
> [leonro@server /]$ sudo rdma dev
> 1: mlx5_0: node_type ca fw 3.8.9999 node_guid 5254:00c0:fe12:3455
> sys_image_guid 5254:00c0:fe12:3455
> [leonro@server /]$ sudo rdma dev set mlx5_0 name hfi1_0
> [leonro@server /]$ sudo rdma dev
> 1: hfi1_0: node_type ca fw 3.8.9999 node_guid 5254:00c0:fe12:3455
> sys_image_guid 5254:00c0:fe12:3455
>
> This functionality is done through RDMA netlink and implemented by
> device_rename() function, despite the comment from 2010, which warns
> about downsides of this function, the netdev is still uses, so we will
> use too.
>
> This series was tested with mlx5 devices with/without traffic and with
> non-modified rdma-core.
>
> Thanks
>
> Leon Romanovsky (2):
> RDMA/core: Implement IB device rename function
> RDMA/nldev: Allow IB device rename through RDMA netlink
Thanks, series applied.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
