From: Jonathan Morton <chromatix99@gmail.com>
To: Collin Anderson <cmawebsite@gmail.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] SPDY and VPN
Date: Sun, 1 Sep 2013 23:07:12 +0300 [thread overview]
Message-ID: <33D30627-0E26-4A54-AFAE-64EBF907FA12@gmail.com> (raw)
In-Reply-To: <CAFO84S5Xq7zU3DvVZG5m-=BuRmCxw5sB4D8y7PvW2grwJe095g@mail.gmail.com>
On 1 Sep, 2013, at 11:03 pm, Collin Anderson wrote:
> Any ideas for solving buffer bloat when using SPDY or VPN where one flow can contain both elephants and mice inside of it?
That simply means that FQ-based solutions won't help in the solution. Reducing driver and hardware buffers, and using AQM techniques at the bottleneck, will still have big effects on overall latency.
- Jonathan Morton
prev parent reply other threads:[~2013-09-01 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 20:03 Collin Anderson
2013-09-01 20:07 ` Jonathan Morton [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
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=33D30627-0E26-4A54-AFAE-64EBF907FA12@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cmawebsite@gmail.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