Re: RDMA miniconf: Persistent device naming

[Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>]

On Mon, Jul 31, 2017 at 08:38:13PM +0300, Leon Romanovsky wrote:
> On Mon, Jul 31, 2017 at 11:24:36AM -0600, Jason Gunthorpe wrote:
> > On Mon, Jul 31, 2017 at 08:08:04PM +0300, Leon Romanovsky wrote:
> > > On Mon, Jul 31, 2017 at 11:00:18AM -0600, Jason Gunthorpe wrote:
> > > > On Mon, Jul 31, 2017 at 07:54:53PM +0300, Leon Romanovsky wrote:
> > > > > I want to take RDMA one step more,
> > > > > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> > > > >
> > > > > I called the topic name "persistent", but the right name is "predictable".
> > > >
> > > > Once renaming is possible then having udev rework the names isn't a
> > > > big step anymore.
> > >
> > > You need predictable starting point to perform automatic rename,
> > > currently neither index, neither names are not.
> >
> > udev has all the information needed to produce the naming pattern in
> > the link above.
> >
> > You'd end up with names like rdmap3s1f1 for instance.
> 
> I'm not so convinced that udev scripts digging into various outputs
> (lspci, e.t.c.) are better solution than kernel handles everything
> exactly as netdev.

I'm confused. You linked to PredictableNetworkInterfaceNames, which is
entirely implemented by udev.

The only kernel support for netdev is the ability to rename netdevs,
everything else is done in userspace, by udev on modern systems.

The sooner we get the same kernel API for RDMA the better, I'd run it
over rdma netlink I think.

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html