From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Adel Belkhiri" <adel.belkhiri@gmail.com>
Cc: <dev@dpdk.org>, "Adel Belkhiri" <adel.belkhiri@polymtl.ca>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Ferruh Yigit" <ferruh.yigit@amd.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH] ethdev: optimize activation of fast-path tracepoints
Date: Fri, 13 Sep 2024 21:47:59 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F6E4@smartserver.smartshare.dk> (raw)
In-Reply-To: <20240913175828.21640-1-adel.belkhiri@gmail.com>
> +++ b/lib/ethdev/version.map
> @@ -207,7 +207,8 @@ EXPERIMENTAL {
> rte_flow_dev_dump;
>
> # added in 20.05
> - __rte_ethdev_trace_rx_burst;
> + __rte_ethdev_trace_rx_burst_empty;
> + __rte_ethdev_trace_rx_burst_nonempty;
These two should be moved down below "# added in 24.11" (which is not yet there, so should be added too).
And I don't know why __rte_eth_trace_call_rx_callbacks is not in the version.map file, but I suppose these should be added too:
+ __rte_eth_trace_call_rx_callbacks_empty
+ __rte_eth_trace_call_rx_callbacks_nonempty
Everything else looks good.
With version.map corrected,
Acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2024-09-13 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 17:58 Adel Belkhiri
2024-09-13 19:47 ` Morten Brørup [this message]
2024-09-16 8:25 ` Jerin Jacob
2024-09-16 8:31 ` David Marchand
2024-09-16 8:45 ` Jerin Jacob
2024-09-18 18:45 ` [PATCH v3] ethdev: optimize the " Adel Belkhiri
2024-09-19 16:37 ` Jerin Jacob
2024-09-22 1:07 ` Ferruh Yigit
2024-09-23 15:27 ` Adel Belkhiri
2024-09-20 14:46 ` Patrick Robb
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=98CBD80474FA8B44BF855DF32C47DC35E9F6E4@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=adel.belkhiri@gmail.com \
--cc=adel.belkhiri@polymtl.ca \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
/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).