From: Sebastian Moeller <moeller0@gmx.de>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: sweeping up the bloat
Date: Tue, 16 Jun 2015 20:10:09 +0200 [thread overview]
Message-ID: <17A671BF-59B9-41B2-B629-FFB211A134F4@gmx.de> (raw)
In-Reply-To: <CAA93jw5o4v1NXy8UOxS47zn6_y6Q1f9uSX2WgcVD87aaEs_ScQ@mail.gmail.com>
Dear list,
it seems my reply-all skill got a bit rusty, so here I go again ;) (threading might be broken?)
On Jun 16, 2015, at 19:53 , Dave Taht <dave.taht@gmail.com> wrote:
> [...]
> 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 thought a voip app will pace simply by virtue of having to collect 10-20ms seconds worth of audio before packing this up and send it off. I have not looked at packet captures but my H0 is that there should be one UDP packet every 20ms, which I would call natural or data-driven pacing. I would not be too amazed if in reality instead of 1 packet per 20ms the app would send N packets every N*20ms; sad, yes, but not amazed.
Best Regards
Sebastian
next parent reply other threads:[~2015-06-16 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw5o4v1NXy8UOxS47zn6_y6Q1f9uSX2WgcVD87aaEs_ScQ@mail.gmail.com>
2015-06-16 18:10 ` Sebastian Moeller [this message]
2015-06-16 18:30 ` 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=17A671BF-59B9-41B2-B629-FFB211A134F4@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
/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