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 > >> <arielalmogworkemails@xxxxxxxxx> wrote: > > >>> As of today, there is no single, simple, tool that allows monitoring > >>> and configuration of RDMA stack. > > >> Before tool, what kernel UAPI you thought to use? > > > I'm aware of the following options: > > 1) netlink > > 2) RDMA ABI https://www.spinics.net/lists/linux-rdma/msg43960.html > > 3) ioctl > > 4) write/read > > > > The items 1 and 2 are preferred options and one of the main goals > > for this RFC is to chose between them. > > > > For example, RDMA ABI has native support of querying and discovering > > device capabilities via merge tree feature. > > To make it clear, when you wrote ABI in your initial email, I tend to > think it was sort of unclear to the netdev crowd that you are talking > on new UAPI which is now under the works for the IB subsystem, so with > my netdev community member hat, I got confused... anyway I think it depends on what this tool is supposed to cover, but based on the description, I would start with netlink-only. The only place verbs covers a similar ground is in 'device capabilities' - for some of that you might want to open a new-uAPI verbs fd, but even the capability data from that would not be totally offensive to be accessed over netlink. IMHO netlink should cover almost everything found in sysfs today. I'm also deeply skeptical about driver-specific stuff at this layer, that sounds like a way to make a big mess. 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
