From: Sridhar Pothuganti <sridhar.pothuganti@nxp.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Facing an issue with eth RX/TX call backs
Date: Mon, 17 Oct 2022 04:42:54 +0000 [thread overview]
Message-ID: <PAXPR04MB942270296263242970A8ECD989299@PAXPR04MB9422.eurprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hello All,
I am trying to use the "dpdk-pdump" application to capture the packets. The pdump library is registering the RX/TX callbacks, but the callback pointer is getting NULL in the RX/TX function during packet transmission.
The callbacks are set using the function "rte_eth_add_tx_callback" and the code is using GCC atomic built-in "__atomic_store_n" with memory order "__ATOMIC_RELEASE".
In the "rte_eth_tx_burst" the same pointer is being read using "__atomic_load_n" with memory order "__ATOMIC_RELAXED".
I have gone through the code, and the "pre_tx_burst_cbs" is not being cleared no where else except "rte_eth_remove_tx_callback". But this function is not being called till the termination of pdump application.
Can someone please point me to where am I missing?
Regards,
Sridhar
[-- Attachment #2: Type: text/html, Size: 2910 bytes --]
next reply other threads:[~2022-10-17 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 4:42 Sridhar Pothuganti [this message]
2022-10-17 15:01 ` Stephen Hemminger
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=PAXPR04MB942270296263242970A8ECD989299@PAXPR04MB9422.eurprd04.prod.outlook.com \
--to=sridhar.pothuganti@nxp.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).