From: omer yamac <aomeryamac@gmail.com>
To: users@dpdk.org
Subject: Direct Mem Pool vs Indirect mem pool creation
Date: Fri, 1 Sep 2023 15:47:54 +0300 [thread overview]
Message-ID: <CA+sj1i9PB4zEXJx1UqfJiSqm65YeRHvuQQQiTyAHKqKscCuB8Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Hello,
I need clarification while creating direct/indirect buffers for mbuf. I
couldn't find exact documentation, and I just looked over the fragmentation
test case and saw that two pools were created. One is a
direct pool, and the other is an indirect pool. Here are the methods to
create pools:
direct_pool = rte_pktmbuf_pool_create("FRAG_D_MBUF_POOL",
NUM_MBUFS, BURST, 0,
RTE_MBUF_DEFAULT_BUF_SIZE,
SOCKET_ID_ANY);
indirect_pool = rte_pktmbuf_pool_create("FRAG_I_MBUF_POOL",
NUM_MBUFS, BURST, 0,
0, SOCKET_ID_ANY)
I couldn't see the exact difference. Just the "data_room_size" parameter is
different. If this parameter is 0, then is the pool indirect?
Thanks all
[-- Attachment #2: Type: text/html, Size: 962 bytes --]
next reply other threads:[~2023-09-01 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 12:47 omer yamac [this message]
2023-09-01 13:08 ` Thomas Monjalon
2023-09-01 13:31 ` omer yamac
2023-09-01 21:30 ` Abdullah Ömer Yamaç
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=CA+sj1i9PB4zEXJx1UqfJiSqm65YeRHvuQQQiTyAHKqKscCuB8Q@mail.gmail.com \
--to=aomeryamac@gmail.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).