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: Tue, 10 May 2016 20:04:29 -0600 Message-ID: <20160511020429.GA32766@obsidianresearch.com> References: <20160505181423.GB5957@obsidianresearch.com> <20160506225523.GA21309@obsidianresearch.com> <20160509163537.GA15479@obsidianresearch.com> <20160509191613.GS29160@leon.nu> <20160509195734.GA22669@obsidianresearch.com> <20160510044107.GU29160@leon.nu> <20160510170739.GA2879@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Christoph Lameter Cc: Leon Romanovsky , Matan Barak , "Hefty, Sean" , Doug Ledford , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Majd Dibbiny , Bodong Wang List-Id: linux-rdma@vger.kernel.org On Tue, May 10, 2016 at 07:29:42PM -0500, Christoph Lameter wrote: > > > Exactly, this is why it is posted on the open mailing list where > > > everyone has stage to express their opinion, including these mysterious > > > hardware architecture who cares about future design, but doesn't care about > > > its future support. > > > > Look, if you want linux-rdma to be setting hardware standards then get > > a consensus from the vendors on this idea. > > This is about exporting existing hardware features that are already > available through the standard socket APIs. Eh? How is LSO or RSS available through standard socket APIs? Yes, it is indirectly through the TCP stack, but the actual hardware feature is not directly accessible??? > > This was tried at the Collab summit and I heard several representatives > > strongly say no. > > Hardware standards? I thought we were talking about software and APIs. The LSO, RSS and Timestamp patches all demand very specific hardware functionality for a device to implement the API. It is fundamentally not a 100% software API. Look at the patches. The LSO patch is so bad Sean and Steve couldn't even figure out what the heck the HW feature does. I know what it does, but I can't tell you the fine details of the actual required hardware behavior. How on earth is someone else supposed to ever implement hardware that does this? I still don't understand why this is being forced into libibverbs. dpdk would seem to be the prefered way to access these sorts of features and there is no technical reason why the mlx dpdk provider needs to use libibverbs. Talk directly to /dev/uverbs0 and use udata to enable the universe of nic specific features. For instance, the dpdk community has already done the hard work to figure out how to expose things like LSO to their users - and they actually have multiple vendors providing these features... http://dpdk.org/ml/archives/dev/2014-May/002537.html I guess you are going to tell me you want these features on IB UD transport and dpdk has no support for L2's other than ethernet? 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