From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Sun, Xutao" <xutao.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] examples/vmdq: Fix the core dump issue when mem_pool is more than 34
Date: Fri, 30 Oct 2015 05:54:40 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8D0D7D8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1445922658-4955-1-git-send-email-xutao.sun@intel.com>
> -----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
>
> 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 <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
>
> examples/vmdq/main.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> 1.9.3
prev parent reply other threads:[~2015-10-30 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 7:29 [dpdk-dev] [PATCH] " Xutao Sun
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 ` Wu, Jingjing [this message]
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=9BB6961774997848B5B42BEC655768F8D0D7D8@SHSMSX104.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=xutao.sun@intel.com \
/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).