netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Florian Westphal <fw@strlen.de>,
	Glenn Judd <glenn.judd@morganstanley.com>,
	Nandita Dukkipati <nanditad@google.com>,
	Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH net-next] codel: add ce_threshold attribute
Date: Sat, 9 May 2015 20:23:14 -0400	[thread overview]
Message-ID: <CADVnQy=_R5d_tHKGfoD29Znr=VzL1tHCAkD_10nnPMdMtzJU8g@mail.gmail.com> (raw)
In-Reply-To: <1431122712.22756.43.camel@edumazet-glaptop2.roam.corp.google.com>

On Fri, May 8, 2015 at 6:05 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> For DCTCP or similar ECN based deployments on fabrics with shallow
> buffers, hosts are responsible for a good part of the buffering.
>
> This patch adds an optional ce_threshold to codel & fq_codel qdiscs,
> so that DCTCP can have feedback from queuing in the host.
>
> A DCTCP enabled egress port simply have a queue occupancy threshold
> above which ECT packets get CE mark.
>
> In codel language this translates to a sojourn time, so that one doesn't
> have to worry about bytes or bandwidth but delays.
>
> This makes the host an active participant in the health of the whole
> network.
>
> This also helps experimenting DCTCP in a setup without DCTCP compliant
> fabric.
>
> On following example, ce_threshold is set to 1ms, and we can see from
> 'ldelay xxx us' that TCP is not trying to go around the 5ms codel
> target.
>
> Queue has more capacity to absorb inelastic bursts (say from UDP
> traffic), as queues are maintained to an optimal level.
>
> lpaa23:~# ./tc -s -d qd sh dev eth1
> qdisc mq 1: dev eth1 root
>  Sent 87910654696 bytes 58065331 pkt (dropped 0, overlimits 0 requeues 42961)
>  backlog 3108242b 364p requeues 42961
> qdisc codel 8063: dev eth1 parent 1:1 limit 1000p target 5.0ms ce_threshold 1.0ms interval 100.0ms
>  Sent 7363778701 bytes 4863809 pkt (dropped 0, overlimits 0 requeues 5503)
>  rate 2348Mbit 193919pps backlog 255866b 46p requeues 5503
>   count 0 lastcount 0 ldelay 1.0ms drop_next 0us
>   maxpacket 68130 ecn_mark 0 drop_overlimit 0 ce_mark 72384
> qdisc codel 8064: dev eth1 parent 1:2 limit 1000p target 5.0ms ce_threshold 1.0ms interval 100.0ms
>  Sent 7636486190 bytes 5043942 pkt (dropped 0, overlimits 0 requeues 5186)
>  rate 2319Mbit 191538pps backlog 207418b 64p requeues 5186
>   count 0 lastcount 0 ldelay 694us drop_next 0us
>   maxpacket 68130 ecn_mark 0 drop_overlimit 0 ce_mark 69873
> qdisc codel 8065: dev eth1 parent 1:3 limit 1000p target 5.0ms ce_threshold 1.0ms interval 100.0ms
>  Sent 11569360142 bytes 7641602 pkt (dropped 0, overlimits 0 requeues 5554)
>  rate 3041Mbit 251096pps backlog 210446b 59p requeues 5554
>   count 0 lastcount 0 ldelay 889us drop_next 0us
>   maxpacket 68130 ecn_mark 0 drop_overlimit 0 ce_mark 37780
> ...
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Florian Westphal <fw@strlen.de>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Glenn Judd <glenn.judd@morganstanley.com>
> Cc: Nandita Dukkipati <nanditad@google.com>
> Cc: Neal Cardwell <ncardwell@google.com>
> Cc: Yuchung Cheng <ycheng@google.com>
> ---

Acked-by: Neal Cardwell <ncardwell@google.com>

Very nice. Thanks for doing this, Eric!

neal

  parent reply	other threads:[~2015-05-10  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 22:05 [PATCH net-next] codel: add ce_threshold attribute Eric Dumazet
2015-05-09 21:21 ` Daniel Borkmann
2015-05-10  0:23 ` Neal Cardwell [this message]
2015-05-10 23:50 ` David Miller

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='CADVnQy=_R5d_tHKGfoD29Znr=VzL1tHCAkD_10nnPMdMtzJU8g@mail.gmail.com' \
    --to=ncardwell@google.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=glenn.judd@morganstanley.com \
    --cc=nanditad@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycheng@google.com \
    /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).