From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Van Assche Subject: Re: [RFC] RESEND - rdmatool - tool for RDMA users Date: Wed, 18 Jan 2017 13:45:14 -0800 Message-ID: <5f90fd26-e7bf-bb2a-01f2-6b166f2265e9@sandisk.com> References: <20170118173327.GF32481@mtr-leonro.local> <20170118183127.GC14198@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170118183127.GC14198@obsidianresearch.com> Sender: netdev-owner@vger.kernel.org To: Jason Gunthorpe , Or Gerlitz Cc: Leon Romanovsky , Ariel Almog , "linux-rdma@vger.kernel.org" , Linux Netdev List List-Id: linux-rdma@vger.kernel.org On 01/18/2017 10:31 AM, Jason Gunthorpe wrote: > 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. We would need a very strong argument to introduce a netlink API that duplicates existing sysfs API functionality. Since the sysfs API is extensible, why not extend that API further? E.g. the SCST sysfs API shows that more is possible with sysfs than what most kernel drivers realize. Bart.