public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2] codel: add ce_threshold support to codel & fc_codel
Date: Thu, 21 May 2015 15:25:28 -0700	[thread overview]
Message-ID: <20150521152528.1791629f@urahara> (raw)
In-Reply-To: <1431366295.566.35.camel@edumazet-glaptop2.roam.corp.google.com>

On Mon, 11 May 2015 10:44:55 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> From: Eric Dumazet <edumazet@google.com>
> 
> codel & fq_codel packet schedulers are now able to have a threshold
> for CE marking packets, regardless of the drop/nodrop decision taken by
> CoDel.
> 
> This is particularly useful for dctcp and variants, that do not use
> traditional ECN.
> 
> Note that fq_codel users would have to specify noecn if ce_threshold is
> used, otherwise results would be not very interesting, as ecn is default
> on for fq_codel.
> 
> $ tc -s qdisc show dev eth1
> qdisc codel 8002: root refcnt 45 limit 1000p target 5.0ms ce_threshold
> 1.0ms interval 100.0ms 
>  Sent 4908469888317 bytes 3351813967 pkt (dropped 0, overlimits 0
> requeues 21624365) 
>  rate 37671Mbit 3231836pps backlog 4904740b 250p requeues 21624365 
>   count 0 lastcount 0 ldelay 1.1ms drop_next 0us
>   maxpacket 68130 ecn_mark 0 drop_overlimit 0 ce_mark 410861803
> 
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Applied to net-next branch

      reply	other threads:[~2015-05-21 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 17:44 [PATCH iproute2] codel: add ce_threshold support to codel & fc_codel Eric Dumazet
2015-05-21 22:25 ` Stephen Hemminger [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=20150521152528.1791629f@urahara \
    --to=stephen@networkplumber.org \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.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