From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 702CE133F for ; Wed, 15 Mar 2017 19:19:04 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga105.fm.intel.com with ESMTP; 15 Mar 2017 11:19:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,170,1486454400"; d="scan'208";a="75794114" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.122]) ([10.237.220.122]) by orsmga005.jf.intel.com with ESMTP; 15 Mar 2017 11:19:00 -0700 To: Vincent JARDIN , "O'Driscoll, Tim" , "thomas.monjalon@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> <127aa10b-13d3-0265-dcb5-0639c60898e8@intel.com> <5505728b-8fc7-9e7a-15e4-776392fae9e7@6wind.com> Cc: "Legacy, Allain (Wind River)" , "dev@dpdk.org" , "Jolliffe, Ian (Wind River)" , "Richardson, Bruce" , "Mcnamara, John" , "Wiles, Keith" , "jerin.jacob@caviumnetworks.com" , "stephen@networkplumber.org" , "3chas3@gmail.com" <3chas3@gmail.com> From: Ferruh Yigit Message-ID: <474778d2-4449-44fe-fd00-0005f7da73fc@intel.com> Date: Wed, 15 Mar 2017 18:18:59 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <5505728b-8fc7-9e7a-15e4-776392fae9e7@6wind.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v4 00/17] Wind River Systems AVP PMD vs virtio? 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: Wed, 15 Mar 2017 18:19:04 -0000 On 3/15/2017 2:08 PM, Vincent JARDIN wrote: > Le 15/03/2017 à 12:29, Ferruh Yigit a écrit : >> The scope of the patch is limited to PMD. >> As long as it is maintained, it is good to have alternative approaches. > > From your logic, then, how many PMDs can be accepted? > > See my previous email: techboard should not bypass discussion of the > dev@ mailing list. I believe that the question for the techboard is > about the number of PMDs that we can get into the DPDK: if any PMDs can > get in, so AVP, fail-safe, xyz, whatever the models that are proposed. > We could even get 2 PMDs of a same (v)NIC, but with different > implementation-designs. There is difference between code duplication, and providing alternative solutions. Agree that we should prevent duplication. And what is bad if number of the PMDs increased, again as long as they are owned/maintained? If not maintained properly, they can be removed as recent net/mpipe example. I believe PMDs are a little different from rest of DPDK, because of their scope, it is easy to exclude any of them without effecting rest, and it is good to have alternative solutions, so user can pick one works best for her, and natural selection can do its work here too. > > Best regards, > Vincent >