DPDK patches and discussions
 help / color / mirror / Atom feed
From: Xutao Sun <xutao.sun@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] examples/vmdq: Fix the core dump issue when mem_pool is more than 34
Date: Tue, 13 Oct 2015 15:29:25 +0800	[thread overview]
Message-ID: <1444721365-1065-1-git-send-email-xutao.sun@intel.com> (raw)

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.

Signed-off-by: Xutao Sun <xutao.sun@intel.com>
---
 examples/vmdq/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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>
 
-#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

             reply	other threads:[~2015-10-13  7:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  7:29 Xutao Sun [this message]
2015-10-13  7:59 ` De Lara Guarch, Pablo
2015-10-15  7:54   ` Sun, Xutao
2015-10-27  5:10 ` [dpdk-dev] [PATCH v2] " Xutao Sun
2015-10-27  7:55   ` De Lara Guarch, Pablo
2015-10-27  8:22     ` Sun, Xutao
2015-10-27  8:58   ` [dpdk-dev] [PATCH v3] " Xutao Sun
2015-10-29  7:53     ` De Lara Guarch, Pablo
2015-12-07  1:46       ` Thomas Monjalon
2015-10-30  5:54   ` [dpdk-dev] [PATCH v2] " Wu, Jingjing
     [not found] <1442814327-29336-1-git-send-email-xutao.sun@intel.com>
2015-09-21  6:43 ` [dpdk-dev] [PATCH] " Wu, Jingjing
2015-09-21  7:19   ` Xu, Qian Q

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1444721365-1065-1-git-send-email-xutao.sun@intel.com \
    --to=xutao.sun@intel.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).