From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: abi change announce Date: Thu, 30 Jul 2015 12:18:41 +0200 Message-ID: <27164357.IJ0XWy5v3t@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Xie, Huawei" , nhorman@tuxdriver.com Return-path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 4FA7DC438 for ; Thu, 30 Jul 2015 12:19:57 +0200 (CEST) Received: by wibxm9 with SMTP id xm9so62000714wib.1 for ; Thu, 30 Jul 2015 03:19:57 -0700 (PDT) In-Reply-To: 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" 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?