From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>,
Jasvinder Singh <jasvinder.singh@intel.com>,
cristian.dumitrescu@intel.com, ferruh.yigit@intel.com,
jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com,
stephen@networkplumber.org
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes
Date: Mon, 13 May 2019 15:56:08 +0200 [thread overview]
Message-ID: <7546919.VKN3ZiIKuY@xps> (raw)
In-Reply-To: <6527befa-11bc-6c75-b01c-5539a8afe3b3@intel.com>
29/04/2019 12:31, Mohammad Abdul Awal:
> On 24/04/2019 13:37, Jasvinder Singh wrote:
> > Add deprecation note for making changes in data structures, APIs
> > and macros in order to have more traffic classes, flexible
> > mapping of pipe queues to traffic classes, subport level
> > configuration of pipes and queues, etc. These changes are aligned
> > to improvements suggested in the RFC-
> > https://mails.dpdk.org/archives/dev/2018-November/120035.html
> >
> > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> > Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> > ---
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > +* sched: To allow more traffic classes, flexible mapping of pipe queues to
> > + traffic classes, and subport level configuration of pipes and queues
> > + changes will be made to macros, data structures and API functions defined
> > + in "rte_sched.h". These changes are aligned to improvements suggested in the
> > + RFC https://mails.dpdk.org/archives/dev/2018-November/120035.html.
>
> Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Acked-by : Reshma Pattan <reshma.pattan@intel.com>
There are only 2 acks for this change.
Any other opinion? yes or no?
next prev parent reply other threads:[~2019-05-13 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 12:37 Jasvinder Singh
2019-04-24 12:37 ` Jasvinder Singh
2019-04-29 10:31 ` Mohammad Abdul Awal
2019-04-29 10:31 ` Mohammad Abdul Awal
2019-05-13 13:56 ` Thomas Monjalon [this message]
2019-05-13 13:56 ` Thomas Monjalon
2019-05-13 13:59 ` Singh, Jasvinder
2019-05-13 13:59 ` Singh, Jasvinder
2019-05-13 14:12 ` Thomas Monjalon
2019-05-13 14:12 ` Thomas Monjalon
2019-05-13 21:31 ` Thomas Monjalon
2019-05-13 21:31 ` Thomas Monjalon
2019-04-30 15:18 ` Pattan, Reshma
2019-04-30 15:18 ` Pattan, Reshma
2020-07-16 10:28 Savinay Dharmappa
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=7546919.VKN3ZiIKuY@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jasvinder.singh@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=stephen@networkplumber.org \
/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).