From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 0/5] netvsc changes for 18.11 Date: Fri, 31 Aug 2018 08:15:16 -0700 Message-ID: <20180831081516.638d4be4@xeon-e3> References: <20180830223512.21297-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Matan Azrad , dev@dpdk.org, Thomas Monjalon , Shahaf Shuler To: Ferruh Yigit Return-path: Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com [209.85.215.195]) by dpdk.org (Postfix) with ESMTP id 2BC1A1AEF0 for ; Fri, 31 Aug 2018 17:15:24 +0200 (CEST) Received: by mail-pg1-f195.google.com with SMTP id r1-v6so5581483pgp.11 for ; Fri, 31 Aug 2018 08:15:24 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, 31 Aug 2018 13:04:18 +0100 Ferruh Yigit 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?