Re: [dpdk-dev] [PATCH] examples/vmdq: Fix the core dump issue when mem_pool is more than 34

["Wu, Jingjing" <jingjing.wu@intel.com>]

> -----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
> 
> 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>
Acked-by: Jingjing Wu <jingjing.wu@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