From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent JARDIN Subject: Re: [PATCH v4 00/17] Wind River Systems AVP PMD vs virtio? Date: Wed, 15 Mar 2017 15:02:11 +0100 Message-ID: <3cecedcd-a970-9c47-1285-561f6a8bd147@6wind.com> References: <1488414008-162839-1-git-send-email-allain.legacy@windriver.com> <1489432593-32390-1-git-send-email-allain.legacy@windriver.com> <4b3a0ff4-3d19-8e4b-0cbf-2a08e6433285@6wind.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA7231E927@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: "Yigit, Ferruh" , "dev@dpdk.org" , "Jolliffe, Ian (Wind River)" , "Richardson, Bruce" , "Mcnamara, John" , "Wiles, Keith" , "thomas.monjalon@6wind.com" , "jerin.jacob@caviumnetworks.com" , "stephen@networkplumber.org" , "3chas3@gmail.com" <3chas3@gmail.com> To: "O'Driscoll, Tim" , "Legacy, Allain (Wind River)" Return-path: Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id 5D2732C49 for ; Wed, 15 Mar 2017 15:02:15 +0100 (CET) Received: by mail-wm0-f42.google.com with SMTP id n11so88427998wma.1 for ; Wed, 15 Mar 2017 07:02:15 -0700 (PDT) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA7231E927@IRSMSX108.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Le 15/03/2017 à 05:10, O'Driscoll, Tim a écrit : >> so, still an nack because: >> - no performance data of avp vs virtio, > I don't think it should be a requirement for Allain to provide performance data in order to justify getting this accepted into DPDK. Keith pointed out in a previous comment on this patch set that even if performance is the same as virtio, there might still be other reasons why people would want to use it. > >> - 2013 is gone, >> - it unfocuses from virtio. Tim, you get it wrong, it IS the major point: if AVP is good in performance, then an alternative to virtio is needed. Please, stop turning around the topic, and send facts/numbers that demonstrate that there is a value in having alternative to virtio. Currently, the only argument is a code developed in 2013 needs to be upstreamed because vhost-user was not available in 2013. Best regards, Vincent