On Mon, Jul 31, 2017 at 11:43:12AM -0600, Jason Gunthorpe wrote: > 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. I linked to that article to save copy/paste of advantages of such scheme. > > The only kernel support for netdev is the ability to rename netdevs, > everything else is done in userspace, by udev on modern systems. I planned to take a deep look on the gaps prior to LPC, but in meanwhile, you are right and it is done in udev since 197. > > The sooner we get the same kernel API for RDMA the better, I'd run it > over rdma netlink I think. Nice, I found who will present it :) Can you prepare short topic about it? > > Jason
Attachment:
signature.asc
Description: PGP signature
