DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Feifei Wang" <Feifei.Wang2@arm.com>, <dev@dpdk.org>
Cc: "nd" <nd@arm.com>,
	"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
	"Ruifeng Wang" <Ruifeng.Wang@arm.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	"Ferruh Yigit" <ferruh.yigit@amd.com>, <thomas@monjalon.net>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"nd" <nd@arm.com>, "nd" <nd@arm.com>
Subject: RE: [PATCH] doc: announce ethdev operation struct changes
Date: Thu, 13 Jul 2023 14:50:49 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87A68@smartserver.smartshare.dk> (raw)
In-Reply-To: <AS8PR08MB7718775CCB56308813F337F8C837A@AS8PR08MB7718.eurprd08.prod.outlook.com>

> From: Feifei Wang [mailto:Feifei.Wang2@arm.com]
> Sent: Thursday, 13 July 2023 04.37
> 
> > From: Feifei Wang
> > Sent: Tuesday, July 4, 2023 4:17 PM
> >
> > > From: Feifei Wang <feifei.wang2@arm.com>
> > > Sent: Tuesday, July 4, 2023 4:10 PM
> > >
> > > To support mbufs recycle mode, announce the coming ABI changes from
> > > DPDK 23.11.
> > >
> > > Signed-off-by: Feifei Wang <feifei.wang2@arm.com>
> > > Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > > ---
> > >  doc/guides/rel_notes/deprecation.rst | 4 ++++
> > >  1 file changed, 4 insertions(+)
> > >
> > > diff --git a/doc/guides/rel_notes/deprecation.rst
> > > b/doc/guides/rel_notes/deprecation.rst
> > > index 66431789b0..c7e1ffafb2 100644
> > > --- a/doc/guides/rel_notes/deprecation.rst
> > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > @@ -118,6 +118,10 @@ Deprecation Notices
> > >    The legacy actions should be removed
> > >    once ``MODIFY_FIELD`` alternative is implemented in drivers.
> > >
> > > +* ethdev: The Ethernet device data structure ``struct rte_eth_dev``
> > > +and
> > > +  the fast-path ethdev flat array ``struct rte_eth_fp_ops`` will be
> > > +updated
> > > +  with new fields to support mbufs recycle mode from DPDK 23.11.
> > > +
> > >  * cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
> > >    to have another parameter ``qp_id`` to return the queue pair ID
> > >    which got error interrupt to the application,
> > > --
> > > 2.25.1
> 
> Ping~

Acked-by: Morten Brørup <mb@smartsharesystems.com>


  reply	other threads:[~2023-07-13 12:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  8:10 Feifei Wang
2023-07-04  8:17 ` Feifei Wang
2023-07-13  2:37   ` Feifei Wang
2023-07-13 12:50     ` Morten Brørup [this message]
2023-07-17  8:28       ` Andrew Rybchenko
2023-07-05 11:32 ` Konstantin Ananyev
2023-07-13  7:52   ` Ferruh Yigit
2023-07-28 14:56 ` Thomas Monjalon
2023-07-28 15:04   ` Thomas Monjalon
2023-07-28 15:08   ` Morten Brørup
2023-07-28 15:20     ` Thomas Monjalon
2023-07-28 15:33       ` Morten Brørup
2023-07-28 15:37         ` Thomas Monjalon
2023-07-28 15:55           ` Morten Brørup
2023-08-01  3:19             ` Feifei Wang

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=98CBD80474FA8B44BF855DF32C47DC35D87A68@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=Feifei.Wang2@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=nd@arm.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).