From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: cristian.dumitrescu@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/3] sched: patches for 2.2
Date: Fri, 04 Mar 2016 16:00:57 +0100 [thread overview]
Message-ID: <5760276.6KREI08Oct@xps13> (raw)
In-Reply-To: <1448822809-8350-1-git-send-email-stephen@networkplumber.org>
2015-11-29 10:46, Stephen Hemminger:
> This is the last round of sched updates for 2.2. It is based
> on code changes (extensively) tested by QA and used in the vRouter.
>
> Stephen Hemminger (3):
> rte_sched: keep track of RED drops
> rte_sched: introduce reciprocal divide
> rte_sched: eliminate floating point in calculating byte clock
Cristian, what is the status of this series, please?
next prev parent reply other threads:[~2016-03-04 15:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 18:46 [PATCH 0/3] sched: patches for 2.2 Stephen Hemminger
2015-11-29 18:46 ` [PATCH 1/3] rte_sched: keep track of RED drops Stephen Hemminger
2015-11-29 22:12 ` Thomas Monjalon
2015-11-30 17:47 ` [PATCH] rte_sched: drop deprecation notice for RED statistics Stephen Hemminger
2015-11-29 18:46 ` [PATCH 2/3] rte_sched: introduce reciprocal divide Stephen Hemminger
2015-12-02 16:45 ` Dumitrescu, Cristian
2015-12-02 16:57 ` Hannes Frederic Sowa
2015-12-02 22:05 ` Stephen Hemminger
2015-11-29 18:46 ` [PATCH 3/3] rte_sched: eliminate floating point in calculating byte clock Stephen Hemminger
2015-12-02 16:48 ` Dumitrescu, Cristian
2015-12-02 22:08 ` Stephen Hemminger
2016-03-04 15:00 ` Thomas Monjalon [this message]
2016-03-08 7:49 ` [PATCH 0/3] sched: patches for 2.2 Dumitrescu, Cristian
2016-03-08 16:33 ` Stephen Hemminger
2016-03-08 19:53 ` Dumitrescu, Cristian
2016-03-08 20:40 ` Stephen Hemminger
2016-03-10 18:41 ` Dumitrescu, Cristian
2016-03-10 18:44 ` Stephen Hemminger
2016-03-10 18:51 ` Dumitrescu, Cristian
2016-03-13 22:25 ` Thomas Monjalon
2016-03-13 22:47 ` Dumitrescu, Cristian
2016-03-13 23:09 ` Thomas Monjalon
2016-03-14 14:40 ` Dumitrescu, Cristian
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=5760276.6KREI08Oct@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.