On Mon, May 30, 2016 at 01:37:35PM +0200, Knut Omang wrote:

quoted

quoted

The separation feels natural, and it allows a more piecemeal approach -
a device can be loaded and tested with one WR at a time. Once ib_mad
gets loaded, a lot of "traffic" is created and just about the whole HCA
under development needs to work to support it.

Adding new device to IB is not an easy task and we clearly need to improve in
that area, however these merges are targeted to the end-user of IB stack which
constantly needs to load all these modules.

In a well configured system, this should all happen automatically -
this is why we have udev? End users should never have to struggle at
this level.

quoted

For the easy development, you can simply revert them in your tree.

:-)
Development and debugging needs aside: Keeping separation between
layers is still a good idea IMHO.

We tried it for the first version of IB router patches which required
conversion ib_netlink to be a module and found ourselves with bazillion
little modules for every file in IB core.