From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 9494B1AEE9 for ; Fri, 31 Aug 2018 18:56:25 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 133B020931; Fri, 31 Aug 2018 12:56:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 31 Aug 2018 12:56:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ZZDbptZXbJf4CQoJwJ0NoJftJb jaDYTcnJWTL+ivM7o=; b=GnRqg0Fbu6VVHBQydzPPC2J6MC6l8NnQS03oSyG9AC niMWYcqnvLFi9rpsNqWAF9ZfO2dfhz+gBn+fqZ3k+jUsonuEZzCReJsRxHQXU1Ut Yq3UMDfUJfA1R/czLC195azHrPQ2Uf/aAGF8ZhbzuYOkUZWg0Who+adWBIMg1Yr8 Y= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZZDbpt ZXbJf4CQoJwJ0NoJftJbjaDYTcnJWTL+ivM7o=; b=I0FBxbWQlz5II7aAyNf673 TNnuhrBkb8ptZY1tKMfCGtOLHCW80xGnld1OAHh+n1t4Ogk0aNzncd7bB+58vVec sO0s+wBVkbBrygq4MA+pbLQ8/Xo161Aha5DxEoY0ePxubiofQkSbxDrLiOynXoCc hFhzf1Q1g91hnpkqDVVlghQzPgQGRl2U8sCGsyU7WfOPkEiHm61flCoOmAG34jTc tdD5RERTKurOObmMAY9FwdD+hmszTPr8Rmf/yzsUsi4+C86FP4q/90aOrP3DDfA8 nj19v6/7nMFQMrMLl+6bbLjbAiUh/Xrc4VJQZXlpEY7eY4p25VYzhAxxV/pHiKXg == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 84789E4693; Fri, 31 Aug 2018 12:56:23 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger , Ferruh Yigit Cc: Matan Azrad , dev@dpdk.org, Shahaf Shuler Date: Fri, 31 Aug 2018 18:56:22 +0200 Message-ID: <2804862.VNJHKtu7v1@xps> In-Reply-To: <20180831081516.638d4be4@xeon-e3> References: <20180830223512.21297-1-stephen@networkplumber.org> <20180831081516.638d4be4@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/5] netvsc changes for 18.11 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 16:56:25 -0000 31/08/2018 17:15, Stephen Hemminger: > 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? 19.11 would be reasonnable target to deprecate vdev_netvsc.