DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: topperxin <topperxin@126.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
	olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru
Subject: Re: [dpdk-users] what's the cache size of rte_mempool_create()?
Date: Wed, 29 Sep 2021 12:48:24 +0200	[thread overview]
Message-ID: <8006744.t41pDv0jej@thomas> (raw)
In-Reply-To: <5a53ec0f.4a37.17bc4b38e33.Coremail.topperxin@126.com>

+Cc mempool maintainers

08/09/2021 11:18, topperxin:
> HI list
>          A question about the value of cache size of rte_mempool_crate() function, the defination of this function like below:
> 
> 
>         struct rte_mempool *
> 
> rte_mempool_create(const char *name, unsigned n, unsigned elt_size,
> 
>                    unsigned cache_size, unsigned private_data_size,
> 
>                    rte_mempool_ctor_t *mp_init, void *mp_init_arg,
> 
>                    rte_mempool_obj_cb_t *obj_init, void *obj_init_arg,
> 
>                    int socket_id, unsigned flags);
> 
> 
> 
> 
> 
>      My question is : what's cache_size value means ? what's difference between if I set cache_size = 0 and cache_size = 512 ?
>      I get some information from the the dpdk 20.11 it said that, if we set cache size to 0 , it can be useful to avoid losing objects in cache , I can't understand this point, does it mean
>      that if we set the cache size to non zero, it will suffer the risk that some packages will lost ? right ?
> 
> 
>      Thanks for your tips.
> 
> 
>      BR.





  reply	other threads:[~2021-09-29 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  9:18 topperxin
2021-09-29 10:48 ` Thomas Monjalon [this message]
2021-09-29 20:25   ` Olivier Matz

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=8006744.t41pDv0jej@thomas \
    --to=thomas@monjalon.net \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=olivier.matz@6wind.com \
    --cc=topperxin@126.com \
    --cc=users@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).