On Wed, Jan 18, 2017 at 07:50:26PM +0200, Or Gerlitz wrote: > On Wed, Jan 18, 2017 at 7:33 PM, Leon Romanovsky wrote: > > On Wed, Jan 18, 2017 at 06:48:21PM +0200, Or Gerlitz wrote: > >> On Wed, Jan 18, 2017 at 5:19 PM, Ariel Almog > >> <arielalmogworkema...@gmail.com> wrote: > > >> What's wrong with the RDMA netlink infrastructure?! it's there for > >> years and used > >> for various cases by MLNX, did you look on the code? > > > Nothing wrong, it is one of the valuable options and will be used if > > community decides to put this tool under iproute2/ethtool umbrella. > > yeah, using netlink sounds good to me, and where you package/maintain > the tool is of 2nd order, 1st decide what UAPI you wonna use. So far > netlink was good for what bunch of use-cases needed.
Or, This tool is for users and they don't care how it is implemented underneath. We want to provide to our users similar experience as they have already with other tools and package/maintainability is important for them more than kernel UAPI. Ariel came with a small set of initial functionalities, but it doesn't say we should limit ourselves. > > Or. > > >> cea05ea IB/core: Add flow control to the portmapper netlink calls > >> ae43f82 IB/core: Add IP to GID netlink offload > >> 2ca546b IB/sa: Route SA pathrecord query through netlink > >> 753f618 RDMA/cma: Add support for netlink statistics export > >> b2cbae2 RDMA: Add netlink infrastructure > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
signature.asc
Description: PGP signature
