From: Gadre Nayan <gadrenayan@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Using preallocated mempool in pipeline
Date: Wed, 23 Oct 2019 11:22:57 +0530 [thread overview]
Message-ID: <CAKJ7aR7iLHZaqXY0FS+9rgqnYHrkMrDocOi-NKjZbh4VPL-QSQ@mail.gmail.com> (raw)
Hi,
My cli config looks like the following:
App.cli
mempool MEMPOOL0 buffer 16384 pool 32K cache 256 cpu 0
If i wanted to use this MEMPOOL0 in my pipeline I would use the
following config:
pipeline INGRESS port in bsz 32 source mempool MEMPOOL0 file
<file_name> bpp <no of bytes per packet>
I am not clear about the file <file_name> bpp<no of bytes per packet>
options. Please suggest.
I am creating a pipeline which would generate packets instead of using
actual physical ports like LINK RXQ. I can dynamically create a
mempool using
mbuf_pool = rte_pktmbuf_pool_create("MEMPOOL0",
NUM_MBUFS * nb_ports, MBUF_CACHE_SIZE, 0,
RTE_MBUF_DEFAULT_BUF_SIZE, rte_socket_id());
However, I would like to create one at configuration time and
associate it with a pipeline.
How can I achieve this using the configuration file options.
Thanks
G
reply other threads:[~2019-10-23 5:52 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=CAKJ7aR7iLHZaqXY0FS+9rgqnYHrkMrDocOi-NKjZbh4VPL-QSQ@mail.gmail.com \
--to=gadrenayan@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).