DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Adel Belkhiri <adel.belkhiri@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	dev@dpdk.org,  Adel Belkhiri <adel.belkhiri@polymtl.ca>
Subject: Re: [PATCH] ethdev: optimize activation of fast-path tracepoints
Date: Mon, 16 Sep 2024 13:55:25 +0530	[thread overview]
Message-ID: <CALBAE1MxUavMg+Lu+OrKoKNbLW-X=H3=POnY-mggkQN-LPO-Og@mail.gmail.com> (raw)
In-Reply-To: <20240913175828.21640-1-adel.belkhiri@gmail.com>

On Sat, Sep 14, 2024 at 1:59 AM Adel Belkhiri <adel.belkhiri@gmail.com> wrote:
>
> From: Adel Belkhiri <adel.belkhiri@polymtl.ca>
>
> Split the tracepoints rte_ethdev_trace_rx_burst and
> rte_eth_trace_call_rx_callbacks into two separate ones
> for empty and non-empty calls to avoid saturating
> quickly the trace buffer.
>
> Signed-off-by: Adel Belkhiri <adel.belkhiri@polymtl.ca>
> ---

> -                                       nb_rx, nb_pkts);
> +       if (unlikely(nb_rx > 0))

You may consider unlikely(nb_rx)


>         rte_flow_dev_dump;
>
>         # added in 20.05
> -       __rte_ethdev_trace_rx_burst;

Removal of a public symbol breaks the ABI. The good news is that 24.11
can break the ABI.
IMO, It is OK to break this ABI.
Also need to update "Removed items" in doc/guides/rel_notes/release_24_11.rst


> +       __rte_ethdev_trace_rx_burst_empty;
> +       __rte_ethdev_trace_rx_burst_nonempty;
>         __rte_ethdev_trace_tx_burst;
>         rte_flow_get_aged_flows;
>
> --
> 2.34.1
>

  parent reply	other threads:[~2024-09-16  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 17:58 Adel Belkhiri
2024-09-13 19:47 ` Morten Brørup
2024-09-16  8:25 ` Jerin Jacob [this message]
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

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='CALBAE1MxUavMg+Lu+OrKoKNbLW-X=H3=POnY-mggkQN-LPO-Og@mail.gmail.com' \
    --to=jerinjacobk@gmail.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).