From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 0/5] netvsc changes for 18.11
Date: Fri, 31 Aug 2018 18:56:22 +0200
Message-ID: <2804862.VNJHKtu7v1@xps>
References: <20180830223512.21297-1-stephen@networkplumber.org>
 <d22cc852-9474-a194-95be-57773662a36f@intel.com>
 <20180831081516.638d4be4@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Matan Azrad <matan@mellanox.com>, dev@dpdk.org,
 Shahaf Shuler <shahafs@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
 Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 9494B1AEE9
 for <dev@dpdk.org>; Fri, 31 Aug 2018 18:56:25 +0200 (CEST)
In-Reply-To: <20180831081516.638d4be4@xeon-e3>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

31/08/2018 17:15, Stephen Hemminger:
> On Fri, 31 Aug 2018 13:04:18 +0100
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> 
> > On 8/30/2018 11:35 PM, Stephen Hemminger wrote:
> > > These patches are against dpdk-net-next/master because
> > > that is where previous patches have already been merged.
> > > 
> > > Stephen Hemminger (5):
> > >   bus/vmbus: add devargs support
> > >   net/netvsc: allow tuning latency with devargs
> > >   net/netvsc: exhausting transmit descriptors is not an error
> > >   net/netvsc: implement link state change callback
> > >   net/netvsc: integrated VF support  
> > 
> > A highlevel question, since netvsc PMD is upstreamed, can we remove vdev_netvsc one?
> 
> No.
> 
> There are some use cases that still need bifurcated model. And also netvsc PMD
> is still in experimental state and vdev_netvsc/failsafe/tap are more stable.
> 
> I hope maybe by 19.11?

19.11 would be reasonnable target to deprecate vdev_netvsc.