From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 0/5] netvsc changes for 18.11 Date: Fri, 31 Aug 2018 13:04:18 +0100 Message-ID: References: <20180830223512.21297-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, Thomas Monjalon , Shahaf Shuler To: Stephen Hemminger , Matan Azrad Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 692924CAF for ; Fri, 31 Aug 2018 14:04:22 +0200 (CEST) In-Reply-To: <20180830223512.21297-1-stephen@networkplumber.org> Content-Language: en-US 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 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?