From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Swapping membuf pools while running
Date: Thu, 3 Sep 2020 15:03:07 +0200 [thread overview]
Message-ID: <2fc4c1f3-a631-c908-d611-da4effbd4e3e@filipjaniszewski.com> (raw)
Hi,
Is there a way to swap the currently configured mempool for a given
queue while the nic is up and running (so, without reconfiguration)?
The scenario would be:
a) capturing packets (rx_burst) in a loop
b) mempool configured for the queue (while calling
rte_eth_rx_queue_setup) gets filled up
c) before the next rx_burst provide an additional mempool so that the
new one is used.
d) Continue rx bursting using the new mempool
Hopefully the scenario is sufficiently clear.
Ideally I would like to run this scenario using MLX5 NICs, but for what
I was able to see this is not possible, since the DPDK driver code runs
some cache-related operations on the mempool items.
Specifically mlx5_mr_update_mp iterate over all the mbufs by calling
mlx5_mr_update_mp_cb (that does some magic cache-related stuff), which
smells to me like a roadblock for adding some handcrafted function to
swap those buffers (I think there's no explicit API in DPDK for swapping
rx queue mempools).
My idea was just to manipulate mlx5_rxq_data in mlx5_rxq_ctrl (that
contains the mempool pointer) using a new function in DPDK that access
those structures, but all those "update mp" operations above looks like
they're doing something with those mbufs so swapping pool pointer might
mess up a lot.. but not sure, any idea?
Thanks
--
BR, Filip
+48 666 369 823
reply other threads:[~2020-09-03 13:03 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=2fc4c1f3-a631-c908-d611-da4effbd4e3e@filipjaniszewski.com \
--to=contact@filipjaniszewski.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).