DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Adel Belkhiri <adel.belkhiri@gmail.com>,
	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 14:15:17 +0530	[thread overview]
Message-ID: <CALBAE1OkLkkQHgaGVawZv3hzUm96c-nSZU9NxzCODm1nHJY9sw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x3b-uwAQPEZ35Hyn8eOgOoa6vsaabWcJ1wZbxFJ0KpyQ@mail.gmail.com>

On Mon, Sep 16, 2024 at 2:01 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Mon, Sep 16, 2024 at 10:26 AM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> > >         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.
>
> This symbol is in the experimental ABI.
> And in general, I think we should keep the trace symbols as experimental.


Ack.

So I think, we need to update only  "Removed items" in
doc/guides/rel_notes/release_24_11.rst

>
>
> --
> David Marchand
>

  reply	other threads:[~2024-09-16  8:45 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
2024-09-16  8:25 ` Jerin Jacob
2024-09-16  8:31   ` David Marchand
2024-09-16  8:45     ` Jerin Jacob [this message]
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=CALBAE1OkLkkQHgaGVawZv3hzUm96c-nSZU9NxzCODm1nHJY9sw@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=adel.belkhiri@gmail.com \
    --cc=adel.belkhiri@polymtl.ca \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --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).