From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
stephen@networkplumber.org
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH iproute2-next] tc: red: allow setting th_min and th_max to the same value
Date: Fri, 19 Jan 2018 12:37:19 -0800 [thread overview]
Message-ID: <78b62f7d-21be-d6c8-06ef-ae2200a75afa@gmail.com> (raw)
In-Reply-To: <20180116230850.25802-1-jakub.kicinski@netronome.com>
On 1/16/18 3:08 PM, Jakub Kicinski wrote:
> Setting th_min and th_max to the same value may be useful for DCTCP
> deployments. The original DCTCP paper describes it as a simplest way
> of achieving simple ECN threshold marking. Indeed, there doesn't seem
> to be any simpler qdisc in Linux which would allow such a setup today.
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
> ---
> Or should I go ahead and add a DCTCP qdisc? :)
>
> tc/tc_red.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
applied to iproute2-next
prev parent reply other threads:[~2018-01-19 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 23:08 [PATCH iproute2-next] tc: red: allow setting th_min and th_max to the same value Jakub Kicinski
2018-01-19 20:37 ` David Ahern [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=78b62f7d-21be-d6c8-06ef-ae2200a75afa@gmail.com \
--to=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--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).