From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: Upcoming libibverbs release Date: Tue, 28 Jun 2016 15:14:41 -0600 Message-ID: <20160628211441.GA5786@obsidianresearch.com> References: <3b89c411-72be-ddc5-5ebf-009eeee29692@redhat.com> <4ec1d8e6-a908-bb49-a137-415856ec6faa@dev.mellanox.co.il> <20160627181758.GD23540@obsidianresearch.com> <20160628050246.GB3584@leon.nu> <20160628162028.GA27518@obsidianresearch.com> <20160628170549.GE3584@leon.nu> <022001d1d170$fda2c3e0$f8e84ba0$@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <022001d1d170$fda2c3e0$f8e84ba0$@opengridcomputing.com> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve Wise Cc: 'Leon Romanovsky' , 'Yishai Hadas' , 'Doug Ledford' , 'linux-rdma' , 'Yishai Hadas' , 'Matan Barak' , 'Majd Dibbiny' , talal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Tue, Jun 28, 2016 at 02:12:19PM -0500, Steve Wise wrote: > I haven't been following this (long) thread closely enough, but I hope any new > functionality is not _breaking_ existing applications from using _currently > supported_ providers? I thought all this CQ accessor cruft was backwards > compatible. Perhaps I'm wrong? As merged, the new API simply does not work without provider support. The old API keeps working of course. The fundamental question is if it is acceptable for libibverbs to ship a new core provider agnostic API (cq polling) that is optional depending on provider. I say no, that is not acceptable. 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