From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 108EE1B51C for ; Thu, 18 Apr 2019 03:11:18 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2019 18:11:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,364,1549958400"; d="scan'208";a="162582758" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.206]) by fmsmga002.fm.intel.com with ESMTP; 17 Apr 2019 18:11:17 -0700 Date: Thu, 18 Apr 2019 09:05:30 +0800 From: Ye Xiaolong To: Markus Theil Cc: dev@dpdk.org Message-ID: <20190418010530.GA5184@intel.com> References: <20190403095939.GA32340@intel.com> <56ce5855b02d47a085a8d36451561c400f0b039c.camel@debian.org> <0dde8c20e9992047f29d39ad45dcf511244a5297.camel@debian.org> <80c81c0c-cf64-59f8-a592-26cd865fbd89@intel.com> <37073834d0b9a9f5a6e9f39bac3adc5eb29779ab.camel@debian.org> <5bc49c51-04f4-6f73-889d-d3c0ff749784@intel.com> <20190403142217.GA36385@intel.com> <6f660657-d488-1121-126a-a38c9744b1eb@intel.com> <20190403155741.GE36385@intel.com> <34359a7b-f2c8-81f2-8a49-f1238e8dfbf0@tu-ilmenau.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <34359a7b-f2c8-81f2-8a49-f1238e8dfbf0@tu-ilmenau.de> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [BUG] net/af_xdp: Current code can only create one af_xdp device 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: Thu, 18 Apr 2019 01:11:19 -0000 Hi, Markus On 04/17, Markus Theil wrote: >I tested the new af_xdp based device on the current master branch and >noticed, that the usage of static mempool names allows only for the >creation of a single af_xdp vdev. If a second vdev of the same type gets >created, the mempool allocation fails. Thanks for reporting, could you paste the cmdline you used and the error log? Are you referring to ring creation or mempool creation? Thanks, Xiaolong > >Best regards, >Markus Theil From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 933A6A00E6 for ; Thu, 18 Apr 2019 03:11:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8ABFB1B90B; Thu, 18 Apr 2019 03:11:20 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 108EE1B51C for ; Thu, 18 Apr 2019 03:11:18 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2019 18:11:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,364,1549958400"; d="scan'208";a="162582758" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.206]) by fmsmga002.fm.intel.com with ESMTP; 17 Apr 2019 18:11:17 -0700 Date: Thu, 18 Apr 2019 09:05:30 +0800 From: Ye Xiaolong To: Markus Theil Cc: dev@dpdk.org Message-ID: <20190418010530.GA5184@intel.com> References: <20190403095939.GA32340@intel.com> <56ce5855b02d47a085a8d36451561c400f0b039c.camel@debian.org> <0dde8c20e9992047f29d39ad45dcf511244a5297.camel@debian.org> <80c81c0c-cf64-59f8-a592-26cd865fbd89@intel.com> <37073834d0b9a9f5a6e9f39bac3adc5eb29779ab.camel@debian.org> <5bc49c51-04f4-6f73-889d-d3c0ff749784@intel.com> <20190403142217.GA36385@intel.com> <6f660657-d488-1121-126a-a38c9744b1eb@intel.com> <20190403155741.GE36385@intel.com> <34359a7b-f2c8-81f2-8a49-f1238e8dfbf0@tu-ilmenau.de> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: <34359a7b-f2c8-81f2-8a49-f1238e8dfbf0@tu-ilmenau.de> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [BUG] net/af_xdp: Current code can only create one af_xdp device 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190418010530.ifRfAZVQhVulhfm-lDmZuL8MqcMRWTxBN5Z9cUDcIaw@z> Hi, Markus On 04/17, Markus Theil wrote: >I tested the new af_xdp based device on the current master branch and >noticed, that the usage of static mempool names allows only for the >creation of a single af_xdp vdev. If a second vdev of the same type gets >created, the mempool allocation fails. Thanks for reporting, could you paste the cmdline you used and the error log? Are you referring to ring creation or mempool creation? Thanks, Xiaolong > >Best regards, >Markus Theil