From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Horman Subject: Re: abi change announce Date: Thu, 30 Jul 2015 06:33:43 -0400 Message-ID: <20150730103343.GA24968@hmsreliant.think-freely.org> References: <27164357.IJ0XWy5v3t@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 37236C602 for ; Thu, 30 Jul 2015 12:33:53 +0200 (CEST) Content-Disposition: inline In-Reply-To: <27164357.IJ0XWy5v3t@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jul 30, 2015 at 12:18:41PM +0200, Thomas Monjalon wrote: > 2015-07-30 09:25, Xie, Huawei: > > Hi Thomas: > > I am doing virtio/vhost performance optimization, so there is possibly > > some change, for example to virtio or vhost virtqueue data structure. > > Do i need to announce the ABI change even if the change hasn't been > > determined? > > I have no strong opinion. > It seems strange to announce something which is not known. > You may be able to introduce your change without previous notice by using > NEXT_ABI if not too invasive. > > Neil, an opinion? > Given the process, you can't announce the change until you know what it is, since you need to detail in the announcement what the change is going to be. We have no method to reserve an 'ABI break to be determined later', nor should we. Write the code, then we figure out if ABI needs to change and there is a need to announce. Neil