From: Simon Barber <simon@superduper.net>
To: Jonathan Morton <chromatix99@gmail.com>,
Brandon Applegate <brandon@burn.net>
Cc: Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Wed, 20 Jan 2016 09:32:22 -0800 [thread overview]
Message-ID: <569FC4A6.3040001@superduper.net> (raw)
In-Reply-To: <8E58DE45-9B50-438B-8F0D-C292D8AA517F@gmail.com>
Last I looked at this you can attach a qdisc to a virtual interface, but
there is no backpressure, since the interface is virtual and the real
interface it feeds will never 'stop' accepting packets (since you are
really feeding into another qdisc).
So you can do things like rate pacing, logging, etc.
Simon
On 1/19/2016 4:09 PM, Jonathan Morton wrote:
>> On 20 Jan, 2016, at 01:33, Brandon Applegate <brandon@burn.net> wrote:
>>
>> My topology is ‘on a stick’. I have one gig interface to a managed switch, on which are eth0.666 (outside/wan) and eth0.10 (inside).
>>
>> No matter what I do - my bandwidth is 10% of what it should be. I get approx. 3/4mbit down + 2/3mbit up on dslreports speedtest. Bufferbloat looks great though - A+.
>>
>> Is there something inherent I’m doing wrong ? Something to do with my ‘on a stick’ topology biting me ?
> I’m not sure whether a qdisc can be attached to a virtualised interface in this way. Can you run ‘tc -s qdisc’ and show us the output?
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-01-20 17:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 23:33 Brandon Applegate
2016-01-20 0:09 ` Jonathan Morton
2016-01-20 0:14 ` Brandon Applegate
2016-01-20 2:36 ` Jonathan Morton
2016-01-20 17:32 ` Simon Barber [this message]
2016-01-20 10:12 ` Alan Jenkins
2016-01-20 10:15 ` Alan Jenkins
2016-01-20 11:47 ` moeller0
2016-01-20 11:43 ` moeller0
2016-01-20 12:06 ` Alan Jenkins
2016-01-20 12:25 ` moeller0
2016-01-20 14:51 ` Brandon Applegate
2016-01-20 15:10 ` moeller0
2016-01-20 15:15 ` Brandon Applegate
2016-01-20 16:05 ` Sebastian Moeller
2016-01-20 16:10 ` Brandon Applegate
2016-01-20 16:32 ` Alan Jenkins
2016-01-20 16:34 ` Brandon Applegate
2016-01-20 16:47 ` Etienne Champetier
2016-01-20 16:54 ` Brandon Applegate
2016-01-20 17:09 ` Etienne Champetier
2016-01-20 17:42 ` moeller0
2016-01-20 17:50 ` Etienne Champetier
2016-01-20 17:40 ` moeller0
2016-01-20 11:30 ` moeller0
2016-01-20 12:37 ` Rich Brown
2016-01-20 14:42 ` Brandon Applegate
2016-01-20 15:30 ` Brandon Applegate
2016-01-20 16:09 ` Sebastian Moeller
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=569FC4A6.3040001@superduper.net \
--to=simon@superduper.net \
--cc=Bloat@lists.bufferbloat.net \
--cc=brandon@burn.net \
--cc=chromatix99@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