From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 9D767282 for ; Mon, 21 Sep 2015 09:19:27 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP; 21 Sep 2015 00:19:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,566,1437462000"; d="scan'208";a="565552224" Received: from pgsmsx106.gar.corp.intel.com ([10.221.44.98]) by FMSMGA003.fm.intel.com with ESMTP; 21 Sep 2015 00:19:25 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by PGSMSX106.gar.corp.intel.com (10.221.44.98) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 21 Sep 2015 15:19:24 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.179]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.110]) with mapi id 14.03.0248.002; Mon, 21 Sep 2015 15:19:13 +0800 From: "Xu, Qian Q" To: "Wu, Jingjing" , "Sun, Xutao" , "dev@dpdk.org" Thread-Topic: [PATCH] examples/vmdq: Fix the core dump issue when mem_pool is more than 34 Thread-Index: AQHQ9DDgfuFYgMoLoE217szaxDei0p5GiJUQgAAHLYA= Date: Mon, 21 Sep 2015 07:19:13 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E01DDEC78@shsmsx102.ccr.corp.intel.com> References: <1442814327-29336-1-git-send-email-xutao.sun@intel.com> <9BB6961774997848B5B42BEC655768F8CE318D@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <9BB6961774997848B5B42BEC655768F8CE318D@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] examples/vmdq: Fix the core dump issue when mem_pool is more than 34 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 07:19:28 -0000 Tested-by: Qian Xu Commit: c36a82f045ae362b76af4f2a53af10a2a4d2d20f Test platform: HSW server OS: Fedora 20 Kernel : 3.18 1. Bind 2ports to igb_uio 2. Run vmdq sample : ./examples/vmdq/build/vmdq_app -n 4 -c 0x1e -- -p 0x3 = --nb-pools 63 3. Send 63 flows with different MAC/VLAN and see the output. 4. No crash at the app, before the app will be core dumped due to the queue= number is too small.=20 Test result: Pass Thanks Qian -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wu, Jingjing Sent: Monday, September 21, 2015 2:43 PM To: Sun, Xutao; dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] examples/vmdq: Fix the core dump issue when= mem_pool is more than 34 > -----Original Message----- > From: Sun, Xutao > Sent: Monday, September 21, 2015 1:45 PM > To: dev@dpdk.org > Cc: Wu, Jingjing; Zhang, Helin; Sun, Xutao > Subject: [PATCH] examples/vmdq: Fix the core dump issue when mem_pool=20 > is more than 34 >=20 > Macro MAX_QUEUES was defined to 128, only allow 16 mem_pools in theory. > When running vmdq_app with more than 34 mem_pools, it will cause the=20 > core_dump issue. > Change MAX_QUEUES to 1024 will solve this issue. >=20 > Signed-off-by: Xutao Sun Acked-by: Jingjing Wu > --- > examples/vmdq/main.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 > diff --git a/examples/vmdq/main.c b/examples/vmdq/main.c index=20 > a142d49..b463cfb 100644 > --- a/examples/vmdq/main.c > +++ b/examples/vmdq/main.c > @@ -69,7 +69,7 @@ > #include > #include >=20 > -#define MAX_QUEUES 128 > +#define MAX_QUEUES 1024 > /* > * For 10 GbE, 128 queues require roughly > * 128*512 (RX/TX_queue_nb * RX/TX_ring_descriptors_nb) per port. > -- > 1.9.3