From: Sebastian Moeller <moeller0@gmx.de>
To: Pete Heist <peteheist@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake latency update
Date: Fri, 10 Feb 2017 12:35:18 +0100 [thread overview]
Message-ID: <70520D3D-D381-44DC-A789-BB1E24FBE3F4@gmx.de> (raw)
In-Reply-To: <CFF7DB98-DFB7-444D-9771-3521594E4CAD@gmail.com>
Hi Pete,
> On Feb 10, 2017, at 12:08, Pete Heist <peteheist@gmail.com> wrote:
>
>
>> On Feb 10, 2017, at 11:31 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>
>>> On 10 Feb, 2017, at 12:05, Pete Heist <peteheist@gmail.com> wrote:
>>>
>>> It means that both the ingress and egress have been redirected over the same IFB device and QoS'd together.
>>
>> Okay, I guessed as much but wanted to be sure.
>>
>> I can’t think of any theoretical reason for these results. Cake’s flow isolation should be robust enough to cope transparently with bidirectional traffic in half-duplex mode. As you say, a C2D should easily be able to keep up, and at these modest rates I can even discount PCI bandwidth as a concern. So I might need to try to reproduce it here.
>>
>> Does the problem go away if you use a wired link with the same setup otherwise? Or is that inconvenient to try? I have some ath9k equipped machines, but they would need to be set up.
>
> Not a problem. I’ll run a spread of Cake and fq_codel over Ethernet at various bandwidths. It will be through their Apple USB Ethernet adapters (used now for management), which are also connected through a switch, but I think that setup should be fine for this purpose. Should be done in a hour or so and we’ll see…
I believe the Apple USB dongles are fastEthernet only, at least the USB2 types I have available here, which for your tested bandwidth would work, but it will not allow you test at what shaper rate things go pear shaped… Also it wifi creates a bit more CPU load than wired ethernet, it _might_ make sense to concurrently excercise the WIFI cards just to re-create the SIRQ load (but probably not as the first experiment ;) ).
Best Regards
Sebastian
>
> Pete
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-02-10 11:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:36 Pete Heist
2017-02-09 20:52 ` Jonathan Morton
2017-02-10 8:04 ` Pete Heist
2017-02-10 8:49 ` Jonathan Morton
2017-02-10 9:21 ` Pete Heist
2017-02-10 9:29 ` Jonathan Morton
2017-02-10 10:05 ` Pete Heist
2017-02-10 10:31 ` Jonathan Morton
2017-02-10 11:08 ` Pete Heist
2017-02-10 11:35 ` Sebastian Moeller [this message]
2017-02-10 12:21 ` Pete Heist
2017-02-12 12:43 ` Pete Heist
2017-02-12 13:08 ` Dave Taht
2017-02-12 14:12 ` Pete Heist
2017-02-12 16:37 ` Pete Heist
2017-02-12 16:41 ` Jonathan Morton
2017-02-12 17:15 ` Pete Heist
2017-02-14 10:02 ` Pete Heist
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70520D3D-D381-44DC-A789-BB1E24FBE3F4@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=peteheist@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