From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3] examples/vmdq: Fix the core dump issue when mem_pool is more than 34 Date: Mon, 07 Dec 2015 02:46:12 +0100 Message-ID: <13947396.FBRVKCZ9tp@xps13> References: <1445922658-4955-1-git-send-email-xutao.sun@intel.com> <1445936313-31782-1-git-send-email-xutao.sun@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Sun, Xutao" Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 840CB93E6 for ; Mon, 7 Dec 2015 02:47:24 +0100 (CET) Received: by wmvv187 with SMTP id v187so145643893wmv.1 for ; Sun, 06 Dec 2015 17:47:24 -0800 (PST) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > > 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. > > > > Signed-off-by: Xutao Sun > > Acked-by: Pablo de Lara Applied, thanks