Tue, Jul 04, 2017 at 09:55:37AM CEST, leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org wrote:
Hi,
This is third version of series implementing the RDAMtool - the tool
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]}
What about json output? You will need it sooner than later. It will
prevent you from a lot of headaches if you implement it right away.
Lesson learned...
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jul 10, 2017 at 10:02:30AM +0200, Jiri Pirko wrote:
Tue, Jul 04, 2017 at 09:55:37AM CEST, leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org wrote:
quoted
Hi,
This is third version of series implementing the RDAMtool - the tool
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]}
What about json output? You will need it sooner than later. It will
prevent you from a lot of headaches if you implement it right away.
Lesson learned...
I'm planning to do it in the coming kernel cycle.
Thanks
Mon, Jul 10, 2017 at 06:01:44PM CEST, leon@kernel.org wrote:
On Mon, Jul 10, 2017 at 10:02:30AM +0200, Jiri Pirko wrote:
quoted
Tue, Jul 04, 2017 at 09:55:37AM CEST, leon@kernel.org wrote:
quoted
Hi,
This is third version of series implementing the RDAMtool - the tool
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]}
What about json output? You will need it sooner than later. It will
prevent you from a lot of headaches if you implement it right away.
Lesson learned...
I'm planning to do it in the coming kernel cycle.
Yeah, just consider pushing it in this initial patchset. Makes sense and
saves you troubles. Up to you.