DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change
Date: Wed, 4 Aug 2021 12:31:39 +0000	[thread overview]
Message-ID: <DM4PR12MB5373715567D071452A83F7BEA1F19@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1213d676-914f-757d-e028-749a92f37cb3@oktetlabs.ru>



> -----Original Message-----
> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Sent: Wednesday, August 4, 2021 8:28 PM
> To: Xueming(Steven) Li <xuemingl@nvidia.com>
> Cc: dev@dpdk.org; Ray Kinsella <mdr@ashroe.eu>
> Subject: Re: [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change
> 
> On 8/2/21 4:10 PM, Xueming Li wrote:
> > This patch announces the parameter change of eth_queue_release_t
> > callback API to eth_dev_ops in DPDK v21.11.
> >
> > [1] mail list discussion:
> > https://mails.dpdk.org/archives/dev/2021-July/215654.html
> >
> > Signed-off-by: Xueming Li <xuemingl@nvidia.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 d9c0e65921..c38aebe99d 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -131,6 +131,9 @@ Deprecation Notices
> >     consistent with existing outer header checksum status flag naming, which
> >     should help in reducing confusion about its usage.
> >
> > +* ethdev: queue release callback parameter will be changed to device
> > +and queue
> > +  ID to align with other queue configureation callback.
> > +
> >   * i40e: As there are both i40evf and iavf pmd, the functions of them are
> >     duplicated. And now more and more advanced features are developed on iavf.
> >     To keep consistent with kernel driver's name
> >
> 
> Isn't it an internal callback and no deprecation notice required to change it?

Agree, let's drop this deprecation notice. Thanks for pointing this out.

> 
> "to align with" is a bit weak justification that so huge change is required (really many sources must be fixed). I guess it could be
> required for shared RxQ. If so, it should be mentioned.

      reply	other threads:[~2021-08-04 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 13:10 Xueming Li
2021-08-02 13:10 ` [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and group field Xueming Li
2021-08-04  8:08   ` Slava Ovsiienko
2021-08-04 12:29     ` Andrew Rybchenko
2021-08-07 13:32       ` Jerin Jacob
2021-08-07 19:15         ` Thomas Monjalon
2021-08-04 12:27 ` [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change Andrew Rybchenko
2021-08-04 12:31   ` Xueming(Steven) Li [this message]

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=DM4PR12MB5373715567D071452A83F7BEA1F19@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    /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).