From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH V1 for-next 1/2] IB/core: Report LSO capabilities when querying device Date: Mon, 9 May 2016 14:05:07 -0600 Message-ID: <20160509200507.GA23911@obsidianresearch.com> References: <20160502190619.GB32613@obsidianresearch.com> <1828884A29C6694DAF28B7E6B8A82373AB048E47@ORSMSX109.amr.corp.intel.com> <20160504181135.GA15355@obsidianresearch.com> <21d9307f-766e-9aaa-54d3-207a4a4d5d8c@mellanox.com> <20160505181423.GB5957@obsidianresearch.com> <20160506225523.GA21309@obsidianresearch.com> <20160509163537.GA15479@obsidianresearch.com> <1828884A29C6694DAF28B7E6B8A82373AB04A390@ORSMSX109.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB04A390-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Hefty, Sean" Cc: Christoph Lameter , Matan Barak , Doug Ledford , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Majd Dibbiny , Bodong Wang List-Id: linux-rdma@vger.kernel.org On Mon, May 09, 2016 at 07:11:23PM +0000, Hefty, Sean wrote: > > > An IBTA process? How would that be relevant here? > > > > What do you mean? IBTA is the only multi-vendor body left working on > > standardizing the hardware specification for verbs. > > > > These various recent patches are adding new hardware features to > > verbs. > > > > If you want hardware knowledgeable people to help, then you need to go > > to the forums they are active in. > > > > This isn't just a software exercise. > > Previous changes to the uABI (for example, XRC) were not accepted > until they were standardized by the IBTA. An exception that I'm > aware of are the flow specs. We need to decide as a community what we want to do here, because this uncertain process is getting tiring for everyone. The Collab Summit discussions ended with a general consensus that some things would go to the driver-specific channel, while hardware behavior related to the common uAPI would go through at least a multi-vendor sign off process - like IBTA. We didn't talk about how to expose them to apps in userspace once they were exposed through the kernel. It is pretty obvious the current 'process' isn't working. This new idea that the common uAPI should just be a union of every vendor's unique hardware ideas has not resulted in patches being merged any faster; and I think the quality of the API is not as good now.. Jason -- 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