From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 00/10] rte_sched: enhancements and cleanups
Date: Wed, 25 Nov 2015 00:34:20 +0100 [thread overview]
Message-ID: <2702091.7i3cFHDW9Q@xps13> (raw)
In-Reply-To: <1447437516-19152-1-git-send-email-stephen@networkplumber.org>
2015-11-13 09:58, Stephen Hemminger:
> Hierarchal scheduler changes (resend)
>
> Most of these are cleanups for existing code to make it more compatiable
> with coding style, and eliminate #ifdefs.
>
> The only substantive change is to allow more subports per scheduler
> instance. This was submitted for DPDK 2.1 but since it required some
> ABI finesse to change; the real part of this was held off for 2.2.
>
> Stephen Hemminger (10):
> qos: drop deprecated port hierarchy structure
> qos: cleanup comments
> qos: make debugging configurable
> qos: drop debug #ifdef's for credit check
> qos: remove debug conditional code around ENQUEUE
> qos: drop RTE_SCHED_WRR #define
> qos: cleanup defined constants
> qos: allow enabling SSE optimizations in config
> sched: fix coding style
> sched: allow more subports
Applied with deprecation notice removed, thanks.
What about this change announced as deprecation notice?
+* The scheduler statistics structure will change to allow keeping track of
+ RED actions.
prev parent reply other threads:[~2015-11-24 23:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 17:58 Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 01/10] sched: drop deprecated port hierarchy structure Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 02/10] sched: cleanup comments Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 03/10] sched: make debugging configurable Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 04/10] sched: drop debug #ifdef's for credit check Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 05/10] sched: remove debug conditional code around ENQUEUE Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 06/10] sched: drop RTE_SCHED_WRR #define Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 07/10] sched: cleanup defined constants Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 08/10] sched: allow enabling SSE optimizations in config Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 09/10] sched: fix coding style Stephen Hemminger
2015-11-13 17:58 ` [dpdk-dev] [PATCH v2 10/10] sched: allow more subports Stephen Hemminger
2015-11-24 23:34 ` Thomas Monjalon [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=2702091.7i3cFHDW9Q@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--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).