From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "trix@redhat.com" <trix@redhat.com>,
"Kinsella, Ray" <ray.kinsella@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"gakhil@marvell.com" <gakhil@marvell.com>
Subject: RE: [PATCH v4] doc: announce changes in bbdev related to enum extension
Date: Mon, 27 Jun 2022 20:47:40 +0000 [thread overview]
Message-ID: <BY5PR11MB44518272E5DE628B90B12516F8B99@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BY5PR11MB4451F98F1A0E3CD6D696E4A5F8AF9@BY5PR11MB4451.namprd11.prod.outlook.com>
Hi Thomas,
Kind reminder on this one.
Thanks
Nic
> -----Original Message-----
> From: Chautru, Nicolas
> Sent: Friday, June 17, 2022 9:13 AM
> To: dev@dpdk.org; thomas@monjalon.net
> Cc: trix@redhat.com; Kinsella, Ray <ray.kinsella@intel.com>; Richardson,
> Bruce <bruce.richardson@intel.com>; hemant.agrawal@nxp.com;
> david.marchand@redhat.com; stephen@networkplumber.org; Maxime
> Coquelin <maxime.coquelin@redhat.com>; gakhil@marvell.com
> Subject: RE: [PATCH v4] doc: announce changes in bbdev related to enum
> extension
>
> Hi Thomas,
> Can this one be applied based on your review?
> Thanks
> Nic
>
> > -----Original Message-----
> > From: Maxime Coquelin <maxime.coquelin@redhat.com>
> > Sent: Thursday, June 9, 2022 12:54 AM
> > To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org;
> > gakhil@marvell.com; thomas@monjalon.net
> > Cc: trix@redhat.com; Kinsella, Ray <ray.kinsella@intel.com>;
> > Richardson, Bruce <bruce.richardson@intel.com>;
> > hemant.agrawal@nxp.com; david.marchand@redhat.com;
> > stephen@networkplumber.org
> > Subject: Re: [PATCH v4] doc: announce changes in bbdev related to enum
> > extension
> >
> > Hi Nicolas,
> >
> > On 6/9/22 02:34, Nicolas Chautru wrote:
> > > Intent to resolve in DPDK 22.11 historical usage which prevents
> > > graceful extension of enum and API without troublesome ABI breakage
> > > as well as extending API RTE_BBDEV_OP_FFT for new operation type in
> > > bbdev as well as other new members in existing structures.
> > >
> > > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > > ---
> > > doc/guides/rel_notes/deprecation.rst | 11 +++++++++++
> > > 1 file changed, 11 insertions(+)
> > >
> > > diff --git a/doc/guides/rel_notes/deprecation.rst
> > > b/doc/guides/rel_notes/deprecation.rst
> > > index 4e5b23c..c8ab1ec 100644
> > > --- a/doc/guides/rel_notes/deprecation.rst
> > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > @@ -112,6 +112,17 @@ Deprecation Notices
> > > session and the private data of session. An opaque pointer can be
> exposed
> > > directly to application which can be attached to the ``rte_crypto_op``.
> > >
> > > +* bbdev: ``RTE_BBDEV_OP_TYPE_COUNT`` terminating the
> > > +``rte_bbdev_op_type``
> > > + enum will be deprecated and instead use fixed array size when
> > > +required to allow for
> > > + future enum extension.
> > > + Will extend API to support new operation type
> > > +``RTE_BBDEV_OP_FFT`` as per this
> > > + RFC https://patchwork.dpdk.org/project/dpdk/list/?series=22111
> > > + New members will be added in ``rte_bbdev_driver_info`` to expose
> > > +PMD queue topology inspired
> > > + by this RFC
> > > +https://patches.dpdk.org/project/dpdk/list/?series=22076
> > > + New member will be added in ``rte_bbdev_driver_info`` to expose
> > > +the device status as per
> > > + this RFC https://patches.dpdk.org/project/dpdk/list/?series=23367
> > > + This should be updated in DPDK 22.11.
> > > +
> > > * security: Hide structure ``rte_security_session`` and expose an opaque
> > > pointer for the private data to the application which can be attached
> > > to the packet while enqueuing.
> >
> > Thanks for rewording the notice.
> >
> > Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> >
> > Maxime
next prev parent reply other threads:[~2022-06-27 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 18:37 [PATCH v2] " Nicolas Chautru
2022-03-17 18:37 ` Nicolas Chautru
2022-06-09 0:20 ` [PATCH v3] " Nicolas Chautru
2022-06-09 0:20 ` Nicolas Chautru
2022-06-09 0:34 ` [PATCH v4] " Nicolas Chautru
2022-06-09 0:34 ` Nicolas Chautru
2022-06-09 5:14 ` Hemant Agrawal
2022-06-09 7:53 ` Maxime Coquelin
2022-06-17 16:13 ` Chautru, Nicolas
2022-06-27 20:47 ` Chautru, Nicolas [this message]
2022-06-30 14:52 ` Chautru, Nicolas
2022-07-05 15:45 ` Bruce Richardson
2022-07-17 9:48 ` 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=BY5PR11MB44518272E5DE628B90B12516F8B99@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.com \
--cc=ray.kinsella@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=trix@redhat.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).