From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
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 <dev@dpdk.org>; Thu, 30 Jul 2015 12:19:57 +0200 (CEST)
Received: by wibxm9 with SMTP id xm9so62000714wib.1
 for <dev@dpdk.org>; Thu, 30 Jul 2015 03:19:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=HjShrkei+qZ55vKPz3JeFe5RXppOnlPglI7OGVpfc4g=;
 b=Dy+UE177o78KnVdI3ncajvuxdU5VOQZUikh3TTVPZgKYMp9xI56y914h7sjip2Ftq5
 oRcaRYNZy8S34ZXrV5Gf7SYSw8yU2b3LJXzXdipUmCki1wG4tRl+eNhYPWRUG1JS50/5
 b5VqHTFZHRP+QmPN5WFjXE0+4d2YGij6c+6qCZ5HtPn2ey089kaWgCMFI8bHQxus6Of+
 X4ck/BBJnBvg2ESCnqWEMqvctp+yAEqEG+6mox6x7dantZ/inRqBpYjzoiJY97X+R1+W
 tDp4iMdptSrCiCsumiONfNdjN7O7/AYTsNPg5AdyPI/mkaCgDXoBk9nRO+bFjKQbfT8W
 xrXw==
X-Gm-Message-State: ALoCoQk0C4D62FRK+FWnyXHw7ZWliNx5a0y4QMHcCWbmJ2McWZlEV2m/DtI0hkoqmw7sBBguXEQT
X-Received: by 10.194.187.170 with SMTP id ft10mr85707059wjc.26.1438251597098; 
 Thu, 30 Jul 2015 03:19:57 -0700 (PDT)
Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.151.210])
 by smtp.gmail.com with ESMTPSA id be9sm1039000wjb.26.2015.07.30.03.19.55
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 30 Jul 2015 03:19:56 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xie, Huawei" <huawei.xie@intel.com>, nhorman@tuxdriver.com
Date: Thu, 30 Jul 2015 12:18:41 +0200
Message-ID: <27164357.IJ0XWy5v3t@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <C37D651A908B024F974696C65296B57B2BD6AD0A@SHSMSX101.ccr.corp.intel.com>
References: <C37D651A908B024F974696C65296B57B2BD6AD0A@SHSMSX101.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] abi change announce
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2015 10:19:57 -0000

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?