From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-qos 19.02 PRE-RC1
Date: Fri, 21 Dec 2018 16:26:58 +0000 [thread overview]
Message-ID: <20181221162658.23094-1-cristian.dumitrescu@intel.com> (raw)
malloc: add option --match-allocations (2018-12-20 13:01:08 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-qos
for you to fetch changes up to c7286e56de95b7a3ef2ce4fe91b4ea6422be8481:
app/test-pmd: expand RED queue thresholds to 64 bits (2018-12-20 19:03:47 +0000)
----------------------------------------------------------------
Reshma Pattan (2):
meter: unify packet color definition
mbuf: implement generic format for sched field
Rosen Xu (1):
app/test-pmd: expand RED queue thresholds to 64 bits
Tonghao Zhang (1):
sched: fix memory leak on init
app/test-pmd/cmdline_tm.c | 24 ++---
doc/guides/rel_notes/deprecation.rst | 10 ---
doc/guides/rel_notes/release_19_02.rst | 4 +-
examples/qos_sched/app_thread.c | 7 +-
examples/qos_sched/main.c | 1 +
lib/Makefile | 1 +
lib/librte_ethdev/Makefile | 2 +-
lib/librte_ethdev/meson.build | 2 +-
lib/librte_ethdev/rte_mtr.h | 16 ++--
lib/librte_ethdev/rte_tm.h | 16 ++--
lib/librte_eventdev/rte_event_eth_tx_adapter.h | 18 ++--
lib/librte_mbuf/Makefile | 2 +-
lib/librte_mbuf/meson.build | 2 +-
lib/librte_mbuf/rte_mbuf.h | 119 ++++++++++++++++++++++++-
lib/librte_meter/rte_meter.h | 21 +++--
lib/librte_pipeline/rte_table_action.c | 44 +++------
lib/librte_sched/Makefile | 2 +-
lib/librte_sched/meson.build | 1 +
lib/librte_sched/rte_sched.c | 92 ++++++++-----------
lib/librte_sched/rte_sched.h | 10 ++-
lib/meson.build | 4 +-
test/test/test_sched.c | 9 +-
22 files changed, 245 insertions(+), 162 deletions(-)
reply other threads:[~2018-12-21 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181221162658.23094-1-cristian.dumitrescu@intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).