From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Sivaprasad Tummala <sivaprasad.tummala@amd.com>,
dev@dpdk.org, bruce.richardson@intel.com,
david.marchand@redhat.com, thomas@monjalon.net,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [PATCH] doc: announce deprecation of RTE_CPUFLAG_NUMFLAGS
Date: Tue, 25 Jul 2023 07:18:45 -0700 [thread overview]
Message-ID: <20230725141845.GA3689@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <9a3e841e-9b98-2220-5a65-fea1c184053f@amd.com>
On Tue, Jul 25, 2023 at 09:39:15AM +0100, Ferruh Yigit wrote:
> On 7/12/2023 11:18 AM, Sivaprasad Tummala wrote:
> > To allow new cpu features to be added without ABI breakage,
> > RTE_CPUFLAG_NUMFLAGS will be removed in DPDK 23.11 release.
> >
> > Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > index 8e1cdd677a..92db59d9c2 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -28,6 +28,9 @@ Deprecation Notices
> > the replacement API rte_thread_set_name and rte_thread_create_control being
> > marked as stable, and planned to be removed by the 23.11 release.
> >
> > +* eal: RTE_CPUFLAG_NUMFLAGS will be removed in DPDK 23.11 release. This is
> > + to allow new cpu features to be added without ABI breakage.
> > +
> > * rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
> > not allow for writing optimized code for all the CPU architectures supported
> > in DPDK. DPDK has adopted the atomic operations from
>
> +techboard,
>
> Request for review/ack, patch is to remove ABI restriction to add new
> CPU flags.
Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
next prev parent reply other threads:[~2023-07-25 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 10:18 Sivaprasad Tummala
2023-07-12 10:21 ` Ferruh Yigit
2023-07-12 14:51 ` Hemant Agrawal
2023-07-25 8:39 ` Ferruh Yigit
2023-07-25 8:40 ` Bruce Richardson
2023-07-25 9:24 ` Morten Brørup
2023-07-25 9:36 ` Kevin Traynor
2023-07-25 14:18 ` Tyler Retzlaff [this message]
2023-07-25 14:24 ` Jerin Jacob
2023-07-25 16:45 ` Hemant Agrawal
2023-07-28 10:11 ` Thomas Monjalon
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=20230725141845.GA3689@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=sivaprasad.tummala@amd.com \
--cc=techboard@dpdk.org \
--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).