From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: deprecation notice for sched changes
Date: Mon, 28 Jan 2019 16:28:01 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A404988@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <20190128112756.12516-1-reshma.pattan@intel.com>
Hi,
More details needs to be added to deprecation note which are not clear yet, so self NACK.
Thanks,
Reshma
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Reshma Pattan
> Sent: Monday, January 28, 2019 11:28 AM
> To: dev@dpdk.org
> Cc: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: deprecation notice for sched changes
>
> From: Jasvinder Singh <jasvinder.singh@intel.com>
>
> Add deprecation note for making changes in data structures, APIs and macros in
> order to increase the traffic classes, flexible mapping of pipe queues to traffic
> classes, subport level configuration of pipes, queues sizes, etc.
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index f9a1f8188..22a3ecb35 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -14,6 +14,13 @@ Deprecation Notices
> * kvargs: The function ``rte_kvargs_process`` will get a new parameter
> for returning key match count. It will ease handling of no-match case.
>
> +* sched: The data structures specifying port, subport and pipe
> +parameters, stats,
> + API functions to configure hierarchy, collecting stats, and computing
> +memory
> + footprint will be changed to support more number of traffic classes
> +(TCs),
> + flexible mapping of the pipe queues to traffic classes, subport level
> + configration of the pipes, etc. In addition, the macros defined for
> +building
> + the hierarchy will be reworked to support the flexibility.
> +
> * eal: both declaring and identifying devices will be streamlined in v18.11.
> New functions will appear to query a specific port from buses, classes of
> device and device drivers. Device declaration will be made coherent with the
> --
> 2.17.1
prev parent reply other threads:[~2019-01-28 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:27 Reshma Pattan
2019-01-28 16:28 ` Pattan, Reshma [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=3AEA2BF9852C6F48A459DA490692831F2A404988@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.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).