From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v3 0/6] rte_sched: cleanups and API changes
Date: Mon, 11 May 2015 10:07:45 -0700 [thread overview]
Message-ID: <1431364071-27298-1-git-send-email-stephen@networkplumber.org> (raw)
This is 3rd rev of DPDK changes to QoS scheduler.
The change from last revision was to fix the example and fix whitespace.
Stephen Hemminger (6):
rte_sched: make RED optional at runtime
rte_sched: expand scheduler hierarchy for more VLAN's
rte_sched: keep track of RED drops
rte_sched: allow reading without clearing
rte_sched: don't put tabs in log messages
rte_sched: use correct log level
app/test/test_sched.c | 4 +-
examples/qos_sched/stats.c | 22 ++++++---
lib/librte_mbuf/rte_mbuf.h | 5 +-
lib/librte_sched/rte_sched.c | 113 ++++++++++++++++++++++++++++---------------
lib/librte_sched/rte_sched.h | 62 +++++++++++++++---------
5 files changed, 134 insertions(+), 72 deletions(-)
--
2.1.4
next reply other threads:[~2015-05-11 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 17:07 Stephen Hemminger [this message]
2015-05-11 17:07 ` [dpdk-dev] [PATCH 1/6] rte_sched: make RED optional at runtime Stephen Hemminger
2015-05-11 17:07 ` [dpdk-dev] [PATCH 2/6] rte_sched: expand scheduler hierarchy for more VLAN's Stephen Hemminger
2015-05-11 17:20 ` Neil Horman
[not found] ` <8edea4c81f624728bb5f0476b680c410@BRMWP-EXMB11.corp.brocade.com>
2015-05-11 17:32 ` Stephen Hemminger
2015-05-11 17:43 ` Neil Horman
2015-05-11 17:07 ` [dpdk-dev] [PATCH 3/6] rte_sched: keep track of RED drops Stephen Hemminger
2015-05-11 17:07 ` [dpdk-dev] [PATCH 4/6] rte_sched: allow reading without clearing Stephen Hemminger
2015-05-11 17:07 ` [dpdk-dev] [PATCH 5/6] rte_sched: don't put tabs in log messages Stephen Hemminger
2015-05-11 17:07 ` [dpdk-dev] [PATCH 6/6] rte_sched: use correct log level Stephen Hemminger
2015-05-12 13:20 ` [dpdk-dev] [PATCH v3 0/6] rte_sched: cleanups and API changes Thomas Monjalon
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=1431364071-27298-1-git-send-email-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).