[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170710074325.GA1853@nanopsycho>
Date: Mon, 10 Jul 2017 09:43:25 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Leon Romanovsky <leon@...nel.org>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Doug Ledford <dledford@...hat.com>,
Ariel Almog <ariela@...lanox.com>,
Linux RDMA <linux-rdma@...r.kernel.org>,
Linux Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH iproute2 V3 0/4] RDMAtool
Tue, Jul 04, 2017 at 09:55:37AM CEST, leon@...nel.org wrote:
>Hi,
>
>This is third version of series implementing the RDAMtool - the tool
s/RDAMtool/RDMAtool/
>to configure RDMA devices. The initial proposal was sent as RFC [1] and
>was based on sysfs entries as POC.
>
>The current series was rewritten completely to work with RDMA netlinks as
>a source of user<->kernel communications. In order to achieve that, the
>RDMA netlinks were extensively refactored and modernized [2, 3, 4 and 5].
>
>The following is an example of various runs on my machine with 5 devices
>(4 in IB mode and one in Ethernet mode)
>
>### Without parameters
>$ rdma
>Usage: rdma [ OPTIONS ] OBJECT { COMMAND | help }
>where OBJECT := { dev | link | help }
> OPTIONS := { -V[ersion] | -d[etails]}
Do you plan to add "mon" any time soon?
Powered by blists - more mailing lists