From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jingjing.wu@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 9E30C8D3D
 for <dev@dpdk.org>; Mon, 21 Sep 2015 08:43:25 +0200 (CEST)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga102.jf.intel.com with ESMTP; 20 Sep 2015 23:43:25 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.17,566,1437462000"; d="scan'208";a="809123267"
Received: from pgsmsx104.gar.corp.intel.com ([10.221.44.91])
 by orsmga002.jf.intel.com with ESMTP; 20 Sep 2015 23:43:24 -0700
Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by
 PGSMSX104.gar.corp.intel.com (10.221.44.91) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Mon, 21 Sep 2015 14:43:23 +0800
Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.210]) by
 SHSMSX103.ccr.corp.intel.com ([169.254.4.110]) with mapi id 14.03.0248.002;
 Mon, 21 Sep 2015 14:43:21 +0800
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Sun, Xutao" <xutao.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [PATCH] examples/vmdq: Fix the core dump issue when mem_pool
 is more than 34
Thread-Index: AQHQ9DDgfuFYgMoLoE217szaxDei0p5GiJUQ
Date: Mon, 21 Sep 2015 06:43:19 +0000
Message-ID: <9BB6961774997848B5B42BEC655768F8CE318D@SHSMSX104.ccr.corp.intel.com>
References: <1442814327-29336-1-git-send-email-xutao.sun@intel.com>
In-Reply-To: <1442814327-29336-1-git-send-email-xutao.sun@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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2015 06:43:26 -0000



> -----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
> 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
> core_dump issue.
> Change MAX_QUEUES to 1024 will solve this issue.
>=20
> Signed-off-by: Xutao Sun <xutao.sun@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> ---
>  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
> a142d49..b463cfb 100644
> --- a/examples/vmdq/main.c
> +++ b/examples/vmdq/main.c
> @@ -69,7 +69,7 @@
>  #include <rte_mbuf.h>
>  #include <rte_memcpy.h>
>=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