DPDK usage discussions
 help / color / mirror / Atom feed
From: Igor Gutorov <igootorov@gmail.com>
To: users@dpdk.org
Cc: andrew.rybchenko@oktetlabs.ru, mb@smartsharesystems.com
Subject: Mbuf pool cache size in share-nothing applications
Date: Fri, 4 Oct 2024 16:48:33 +0300	[thread overview]
Message-ID: <CAL7bPf09u_zgRrGvJ8N7e+LskpymvwEt38NKdqC_sYFyUv3f9Q@mail.gmail.com> (raw)

Hi,

I'm a bit confused about certain semantics of `cache_size` in memory
pools. I'm working on a DPDK application where each Rx queue gets its
own mbuf mempool. The memory pools are never shared between lcores,
mbufs are never passed between lcores, and so the deallocation of an
mbuf will happen on the same lcore where it was allocated on (it is a
run-to-completion application). Is my understanding correct, that this
completely eliminates any lock contention, and so `cache_size` can
safely be set to 0?

Also, `rte_pktmbuf_pool_create()` internally calls
`rte_mempool_create()` with the default `flags`. Would there be a
performance benefit in creating mempools manually with the
`RTE_MEMPOOL_F_SP_PUT` and `RTE_MEMPOOL_F_SC_GET` flags set?

Thanks!

Sincerely,
Igor.

                 reply	other threads:[~2024-10-04 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAL7bPf09u_zgRrGvJ8N7e+LskpymvwEt38NKdqC_sYFyUv3f9Q@mail.gmail.com \
    --to=igootorov@gmail.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=mb@smartsharesystems.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).