From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 1/4] vhost: handle VHOST_USER_SET_LOG_BASE request Date: Mon, 07 Dec 2015 03:49:03 +0100 Message-ID: <9938135.oiXrlPQS2m@xps13> References: <1449027793-30975-1-git-send-email-yuanhan.liu@linux.intel.com> <1717599.oECOgsfiks@xps13> <20151207021843.GF29571@yliu-dev.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Victor Kaplansky , "Michael S. Tsirkin" To: Yuanhan Liu Return-path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id BFFAC9436 for ; Mon, 7 Dec 2015 03:50:15 +0100 (CET) Received: by wmec201 with SMTP id c201so145901414wme.0 for ; Sun, 06 Dec 2015 18:50:15 -0800 (PST) In-Reply-To: <20151207021843.GF29571@yliu-dev.sh.intel.com> 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-12-07 10:18, Yuanhan Liu: > On Mon, Dec 07, 2015 at 03:03:24AM +0100, Thomas Monjalon wrote: > > 2015-12-07 10:00, Yuanhan Liu: > > > On Mon, Dec 07, 2015 at 12:07:28AM +0100, Thomas Monjalon wrote: > > > > 2015-12-02 15:53, Panu Matilainen: > > > > > This (and other changes in patch 2 breaks the librte_vhost ABI again, so > > > > > you'd need to at least add a deprecation note to 2.2 to be able to do it > > > > > in 2.3 at all according to the ABI policy. > > > > > > > > > > Perhaps a better option would be adding some padding to the structs now > > > > > for 2.2 since the vhost ABI is broken there anyway. That would at least > > > > > give a chance to keep it compatible from 2.2 to 2.3. > > > > > > > > Please could you point where the vhost ABI is broken in 2.2? > > > > > > Thomas, here are the changes to rte_virtio_net.h: > > > > > > > > > $ git diff 381316f6a225139d22d39b5ab8d50c40607924ca..19d4d7ef2a216b5418d8edb5b004d1a58bba3cc1 \ > > > -- lib/librte_vhost/rte_virtio_net.h > > > [...] > > > > The problem is that the changes are not noticed in the release notes > > and the LIBABIVER is still 1. > > Yeah, my bad. Firstly, I was not aware of it's an ABI change. Secondly, > I was landed to this team in the middle of v2.2 release, so that I have > limited experience of how those works in DPDK community. > > Anyway, it's my fault. I should have realized that in the first time. No it's not your fault, and it does not matter who is responsible. > Should I send a patch to update LIBABIVER to 2 and update release note > now? Yes today or tomorrow please.