On Thu, 2017-05-04 at 21:25 +0300, Leon Romanovsky wrote: > On Thu, May 04, 2017 at 06:10:54PM +0000, Bart Van Assche wrote: > > On Thu, 2017-05-04 at 21:02 +0300, Leon Romanovsky wrote: > > > Following our discussion both in mailing list [1] and at the LPC 2016 [2], > > > we would like to propose this RDMA tool to be part of iproute2 package > > > and finally improve this situation. > > > > Hello Leon, > > > > Although I really appreciate your work: can you clarify why you would like to > > add *RDMA* functionality to an *IP routing* tool? I haven't found any motivation > > for adding RDMA functionality to iproute2 in [1]. > > We are planning to reuse the same infrastructure provided by iproute2, > like netlink parsing, access to distributions, same CLI and same standards. > > Right now, RDMA is already tightened to netdev: iWARP, RoCE, IPoIB, HFI-VNIC. > Many drivers (mlx, qed, i40, cxgb) are sharing code between net and > RDMA. > > I do expect that iproute2 will be installed on every machine with any > type of connection, including IB and OPA. > > So I think that it is enough to be part of that suite and don't invent > our own for one specific tool. Hello Leon, Sorry but to me that sounds like a weak argument for including RDMA functionality in iproute2. There is already a library for communication over netlink sockets, namely libnl. Is there functionality that is in iproute2 but not in libnl and that is needed for the new tool? If so, have you considered to create a new library for that functionality? Thanks, Bart.-- 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
