General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] sweeping up the bloat
Date: Tue, 16 Jun 2015 10:53:12 -0700	[thread overview]
Message-ID: <CAA93jw6Vusa9sQ8ccRUx=3kaZoyx9wuMOuguhkcKNWu9hqtTdQ@mail.gmail.com> (raw)
In-Reply-To: <20150616173306.GA9097@sesse.net>

On Tue, Jun 16, 2015 at 10:33 AM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Tue, Jun 16, 2015 at 10:10:18AM -0700, Dave Taht wrote:
>> As one example: I don't have a firm guideline for how, why or when or
>> when to enable pacing
>
> My guideline is “always”.

As you are the original champion of the idea, sure! :) Certainly
seeing the original paper on pacing thoroughly refuted[1] and
observing the effects on tons of traffic now, I, too am mostly a fan
(aggregation bothers me but it's hard to measure, and fq_codel remains
the right thing for routers, bare metal servers hosting vms, and stuff
that gets hw flow control. IMHO. I would love to be able to turn on
the right things more automagically in all these cases)

But guidelines on how to configure it in applications are missing. As
are when where and how to implement it in DCs, handheld clients,
internal servers and hosts, home routers, slow networks, VMs, and bare
metal servers.

Quic does pacing, so far as I know, entirely in userspace, or does it
rely on sch_fq to do so? Should a VOIP app or server like freeswitch
use it?

I see in the kernel support for sk_pacing_rate, and max_pacing_rate
and it is unclear how/when those options can be of aid and set. I have
never seen the patches for vlc (not that I recall, anyway), and
certainly think that pacing and tcp_notsent_lowat would help things
like x11 tunneling. And I'd like to add correct support for it to
netperf and flent so as to better observe the effects on and off at
various rates, bandwidths, and link layer technologies.

So as you are the expert on this, can I request you write up where to
use it and how? Neednt be one big chunk...

[1] https://reproducingnetworkresearch.wordpress.com/2013/03/13/cs244-13-tcp-pacing-and-buffer-sizing/

>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  reply	other threads:[~2015-06-16 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 17:10 Dave Taht
2015-06-16 17:33 ` Steinar H. Gunderson
2015-06-16 17:53   ` Dave Taht [this message]
2015-06-16 18:32     ` Eric Dumazet
2015-06-16 19:33       ` Dave Taht

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='CAA93jw6Vusa9sQ8ccRUx=3kaZoyx9wuMOuguhkcKNWu9hqtTdQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=sgunderson@bigfoot.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