From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: "David Marchand" <david.marchand@redhat.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: jerinj@marvell.com, Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerinjacobk@gmail.com>,
dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@marvell.com>,
Timothy McDaniel <timothy.mcdaniel@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@oss.nxp.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Liang Ma <liangma@liangbit.com>,
Peter Mccarthy <peter.mccarthy@intel.com>
Subject: Re: [PATCH v2] doc: announce single-event enqueue/dequeue ABI change
Date: Sun, 13 Oct 2024 08:57:23 +0200 [thread overview]
Message-ID: <52eec03e-c3c5-427f-9768-54548c9faa1b@lysator.liu.se> (raw)
In-Reply-To: <CAJFAV8zaEDozyEUz4BpzOVH7PHN9AcO6nC5QYchMxq7RXTivmw@mail.gmail.com>
On 2024-10-11 16:42, David Marchand wrote:
> On Wed, Jul 5, 2023 at 1:18 PM Mattias Rönnblom
> <mattias.ronnblom@ericsson.com> wrote:
>>
>> Announce the removal of the single-event enqueue and dequeue
>> operations from the eventdev ABI.
>>
>> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
>>
>> ---
>> PATCH v2: Fix commit subject prefix.
>> ---
>> doc/guides/rel_notes/deprecation.rst | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
>> index 66431789b0..ca192d838d 100644
>> --- a/doc/guides/rel_notes/deprecation.rst
>> +++ b/doc/guides/rel_notes/deprecation.rst
>> @@ -153,3 +153,11 @@ Deprecation Notices
>> The new port library API (functions rte_swx_port_*)
>> will gradually transition from experimental to stable status
>> starting with DPDK 23.07 release.
>> +
>> +* eventdev: The single-event (non-burst) enqueue and dequeue
>> + operations, used by static inline burst enqueue and dequeue
>> + functions in <rte_eventdev.h>, will be removed in DPDK 23.11. This
>> + simplification includes changing the layout and potentially also the
>> + size of the public rte_event_fp_ops struct, breaking the ABI. Since
>> + these functions are not called directly by the application, the API
>> + remains unaffected.
>
> Looks like it was missed in 23.11, can/should we finish this cleanup in 24.11?
>
>
Yes, sure. Jerin, should I submit a patch?
next prev parent reply other threads:[~2024-10-13 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 8:48 [PATCH] eventdev: " Mattias Rönnblom
2023-07-05 11:12 ` [PATCH v2] doc: " Mattias Rönnblom
2023-07-05 13:00 ` Jerin Jacob
2023-07-05 13:02 ` [EXT] " Pavan Nikhilesh Bhagavatula
2023-07-28 15:51 ` Thomas Monjalon
2023-07-26 12:04 ` Jerin Jacob
2024-10-11 14:42 ` David Marchand
2024-10-13 6:57 ` Mattias Rönnblom [this message]
2024-10-14 7:18 ` Jerin Jacob
2024-10-14 14:40 ` Thomas Monjalon
2024-10-14 14:44 ` David Marchand
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=52eec03e-c3c5-427f-9768-54548c9faa1b@lysator.liu.se \
--to=hofors@lysator.liu.se \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=liangma@liangbit.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=pbhagavatula@marvell.com \
--cc=peter.mccarthy@intel.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
--cc=timothy.mcdaniel@intel.com \
/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).