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 9F80F8E69
 for <dev@dpdk.org>; Fri, 30 Oct 2015 06:54:44 +0100 (CET)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by orsmga102.jf.intel.com with ESMTP; 29 Oct 2015 22:54:43 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,217,1444719600"; d="scan'208";a="839052089"
Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205])
 by fmsmga002.fm.intel.com with ESMTP; 29 Oct 2015 22:54:42 -0700
Received: from shsmsx103.ccr.corp.intel.com (10.239.110.14) by
 fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Thu, 29 Oct 2015 22:54:42 -0700
Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.194]) by
 SHSMSX103.ccr.corp.intel.com ([169.254.4.204]) with mapi id 14.03.0248.002;
 Fri, 30 Oct 2015 13:54:40 +0800
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Sun, Xutao" <xutao.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [PATCH v2] examples/vmdq: Fix the core dump issue when
 mem_pool is more than 34
Thread-Index: AQHREHXqW//HKU4b6UmWeFO6HSj/Y56DjcXg
Date: Fri, 30 Oct 2015 05:54:40 +0000
Message-ID: <9BB6961774997848B5B42BEC655768F8D0D7D8@SHSMSX104.ccr.corp.intel.com>
References: <1444721365-1065-1-git-send-email-xutao.sun@intel.com>
 <1445922658-4955-1-git-send-email-xutao.sun@intel.com>
In-Reply-To: <1445922658-4955-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 v2] 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: Fri, 30 Oct 2015 05:54:45 -0000



> -----Original Message-----
> From: Sun, Xutao
> Sent: Tuesday, October 27, 2015 1:11 PM
> To: dev@dpdk.org
> Cc: Wu, Jingjing; Zhang, Helin; Sun, Xutao
> Subject: [PATCH v2] 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 vmdq_pools in
> theory.
> When running vmdq_app with more than 34 vmdq_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>

> ---
> v2:
>  - rectify the NUM_MBUFS_PER_PORT since MAX_QUEUES has been
> changed
>=20
>  examples/vmdq/main.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>=20
> 1.9.3