Thread (42 messages) flat view 42 messages, 9 authors, 2016-02-24

Re: [patch net-next 3/9] mlx4: Implement port type setting via devlink interface

From: Jiri Pirko <jiri@resnulli.us>
Date: 2016-02-23 12:21:13

Tue, Feb 23, 2016 at 12:26:00PM CET, hannes@stressinduktion.org wrote:
Hi Jiri,

On 22.02.2016 19:31, Jiri Pirko wrote:
quoted
From: Jiri Pirko <redacted>

So far, there has been an mlx4-specific sysfs file allowing user to
change port type to either Ethernet of InfiniBand. This is very
inconvenient.
Again, I want to express my concerns regarding all of this until this will be
integrated into udev/systemd for stable device names. While one can build
wrapper code around devlink to have stable devlink ports, I don't see a
reason to include kernel code which actually has more problems than the sysfs
approach. This harms admins to use those devices and will additionally
require user space to write boiler plate code.
Sysfs is not the place to do this things. It was already discussed here
multiple times. There was and attempt to use configfs, which was also
refused. Netlink is the only place to go. For multiple reasons,
including well defined api and behaviour, notifications, etc.

I think it is quite trivial to teach udev to name devlinkX devices
according to pci address (or any other address). That's all what is
needed here. I don't understand your concerns.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help