From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Steinar H. Gunderson" <sesse@samfundet.no>,
renaud sallantin <renaud.sallantin@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM creeping into L2 equipment
Date: Thu, 20 Mar 2014 16:41:24 -0700 [thread overview]
Message-ID: <1395358884.9114.102.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAA93jw4_M+w_3ZZpYNpQu55c44y7ccvKtTEzYEQotH1gcy+cWA@mail.gmail.com>
On Thu, 2014-03-20 at 13:23 -0700, Dave Taht wrote:
> Well there is some good work in linux 3.14 and beyond, and there was also
> some interesting work on "initial spreading" presented at ietf.
>
> Hopefully patches for this will be available soon.
>
> http://tools.ietf.org/html/draft-sallantin-iccrg-initial-spreading-00
>
> I would certainly like to be able to sanely measure the impact of
> hundreds or thousands of flows in slow start, rather than/in addition to 8 flows
> in congestion avoidance.
As mentioned elsewhere, FQ/pacing does exactly this 'spreading', and not
only for the 'initial' burst, but on all the lifetime of tcp flow, for
example after recovery or idle period.
FQ/pacing is part of linux kernel since 3.12
To play with it, you can set it like that :
tc qdisc replace dev eth0 root fq quantum 1514 initial_quantum 1514
http://lwn.net/Articles/564978/
I believe Steinar had success using FQ/pacing lately, presumably using
SO_MAX_PACING_RATE as well.
next prev parent reply other threads:[~2014-03-20 23:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 14:52 Steinar H. Gunderson
2014-03-18 17:17 ` Dave Taht
2014-03-18 17:53 ` Steinar H. Gunderson
2014-03-19 22:22 ` Steinar H. Gunderson
2014-03-18 18:05 ` Fred Baker (fred)
2014-03-18 18:54 ` Dave Taht
2014-03-20 16:20 ` Toke Høiland-Jørgensen
2014-03-20 16:29 ` Dave Taht
2014-03-20 16:44 ` Toke Høiland-Jørgensen
2014-03-20 17:14 ` Dave Taht
2014-03-20 19:34 ` Aaron Wood
2014-03-20 20:23 ` Dave Taht
2014-03-20 23:41 ` Eric Dumazet [this message]
2014-03-20 23:45 ` Steinar H. Gunderson
2014-03-20 23:54 ` Steinar H. Gunderson
[not found] ` <CAAvOmMtt1RCpBfT1MPNh-2FRhQ1GN4xYbfNPLYJwfP6CaP5vow@mail.gmail.com>
2014-03-21 15:06 ` Eric Dumazet
[not found] ` <CAAvOmMvPpmuW1chTdX86s5sQv6X_c622k8YrjW+hN8e5JV+dzA@mail.gmail.com>
2014-03-21 17:51 ` Eric Dumazet
2014-03-21 18:08 ` Dave Taht
2014-03-21 22:00 ` Eric Dumazet
2014-03-21 22:13 ` Dave Taht
2014-03-23 19:27 ` Eric Dumazet
2014-03-21 13:41 ` Toke Høiland-Jørgensen
2014-03-21 15:39 ` Dave Taht
2014-03-21 16:42 ` Steinar H. Gunderson
2014-03-21 18:34 ` Toke Høiland-Jørgensen
2014-03-24 23:16 ` David Lang
2014-03-20 18:16 ` [Bloat] AQM creeping into L2 equipment / 10G not-for-profit playground at tetaneutral.net Laurent GUERBY
2014-03-18 18:57 ` [Bloat] AQM creeping into L2 equipment Dave Taht
2014-03-18 21:06 ` Steinar H. Gunderson
2014-03-19 13:11 ` Nikolay Shopik
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395358884.9114.102.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=renaud.sallantin@gmail.com \
--cc=sesse@samfundet.no \
/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