DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app test: fix mempool cache_size not match	limited cache_size
Date: Thu, 30 Jul 2015 05:49:05 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8C92AA1@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1438140121-9011-1-git-send-email-yong.liu@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yong Liu
> Sent: Wednesday, July 29, 2015 11:22 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] app test: fix mempool cache_size not match
> limited cache_size
> 
> From: Marvin Liu <yong.liu@intel.com>
> 
> In previous setting, mempool size and cache_size are both 32.
> This is not satisfied with cache_size checking rule by now.
> Cache size should less than CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE and
> mempool size / 1.5.
> 
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
> 
Acked-by: Jingjing Wu <jingjing.wu@intel.com>

> diff --git a/app/test/test_sched.c b/app/test/test_sched.c index
> 1ef6910..7a38db3 100644
> --- a/app/test/test_sched.c
> +++ b/app/test/test_sched.c
> @@ -87,7 +87,7 @@ static struct rte_sched_port_params port_param = {
> 
>  #define NB_MBUF          32
>  #define MBUF_DATA_SZ     (2048 + RTE_PKTMBUF_HEADROOM)
> -#define PKT_BURST_SZ     32
> +#define PKT_BURST_SZ     0
>  #define MEMPOOL_CACHE_SZ PKT_BURST_SZ
>  #define SOCKET           0
> 
> --
> 1.9.3

  reply	other threads:[~2015-07-30  5:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  3:22 Yong Liu
2015-07-30  5:49 ` Wu, Jingjing [this message]
2015-08-03 21:45   ` Thomas Monjalon
2015-08-02 21:26 ` Thomas Monjalon
2015-08-03  0:51   ` Liu, Yong

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=9BB6961774997848B5B42BEC655768F8C92AA1@SHSMSX104.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=dev@dpdk.org \
    --cc=yong.liu@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).