Hi Jason, Bart, On Sat, Oct 8, 2016 at 2:30 AM, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Oct 07, 2016 at 01:51:59PM -0700, Bart Van Assche wrote: > >> Do you think the names of the network interfaces to which the rdma_rxe >> driver should bind should be stored in a separate file? To me this looks >> like a suboptimal approach. Shouldn't we drop the /var/rxe/rxe file >> completely and add a new boolean to the files in which other network >> interface parameters are already stored, e.g. >> /etc/NetworkManager/system-connections/* ? > > I honestly don't know much about how rxe works, I was just looking > at the bogus path. > > In today's world this should probably be handled by adding systemd unit > files to set up rxe.. ?? > > Something with network manager also seems to make some kind of sense > on the surface. > Instead of relying on user land to do configuration of different OS flavors, I am considering to auto create rxe interfaces via netdev notifier for all the network interfaces which gets newly added. May be through some sort of attach()/detach() ops(). netdev driver will have choice to reject/accept such calls. So that mlx4_ib is already loaded, it can reject his call from rdma_rxe. Since the ratio of netdev devices which support RDMA to devices which doesn't support RDMA is much large, I do not intent to add _ops() to netdev but rather to have API through which this can be done. Need to think little more to comeup with RFC. Other than dev envionrments its unlikely that users want to play with PMTU configuration. So I was thinking to do do least amount of configuration using rxe_cfg going forward. > Jason > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
