From: Georgios Amanakis <gamanakis@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Fwd: cake flenter results round 2
Date: Wed, 29 Nov 2017 13:19:57 -0500 [thread overview]
Message-ID: <CACvFP_jwqVj4ZT1=ji4LeQn9R723tycjGYPyLAzqKXdMEKPz3w@mail.gmail.com> (raw)
In-Reply-To: <87tvxdvubi.fsf@nemesis.taht.net>
[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]
I completely neglected this. It turns out sometimes netem drops, sometimes
it doesn't.
This would also explain the different behaviour I am getting (rrul1)
sometimes.
I guess it is because netem doesn't drop in this case.
I am attaching a new file with both cases (I could replicate them again).
Delay's netem and mbox's cake stats are in the txt files.
Is a limit of 4000 a sane value?
Calculated as (0.05s * 900mbit/s / 8bit/byte / 1500bytes/packet)??
George
On Wed, Nov 29, 2017 at 1:00 PM, Dave Taht <dave@taht.net> wrote:
> Georgios Amanakis <gamanakis@gmail.com> writes:
>
> > ---------- Forwarded message ----------
> > From: Georgios Amanakis <gamanakis@gmail.com>
> > Date: Wed, Nov 29, 2017 at 12:50 PM
> > Subject: Re: [Cake] cake flenter results round 2
> > To: Dave Taht <dave@taht.net>
> >
> > To avoid a misunderstanding, the delay parameter in both:
> > "ip netns exec delay tc qdisc replace dev delay.r root netem delay 50ms"
> > "ip netns exec delay tc qdisc replace dev delay.l root netem delay 50ms"
>
> I would strongly suspect you are seeing drops in these qdiscs also
> without the increased limit, at the increased delay, at 900mbit (go
> check with ip netns exec delay tc -s qdisc show)
>
> My original scripts were targeted at 16Mbit/1mbit and thus I didn't
> change the limit.
>
>
[-- Attachment #1.2: Type: text/html, Size: 2107 bytes --]
[-- Attachment #2: ackaggr_netem.tgz --]
[-- Type: application/x-gzip, Size: 195804 bytes --]
next prev parent reply other threads:[~2017-11-29 18:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 14:11 [Cake] " Pete Heist
2017-11-28 15:56 ` Pete Heist
2017-11-28 19:07 ` Dave Taht
2017-11-28 20:35 ` Pete Heist
2017-11-28 22:34 ` Dave Taht
2017-11-28 22:52 ` Dave Taht
2017-11-29 0:16 ` Pete Heist
[not found] ` <CACvFP_iY+KSUgyqrJsmpEjY8Bj5E+vCTwRhojQzUhkE2_7XVXA@mail.gmail.com>
2017-11-29 0:20 ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 3:29 ` [Cake] " Georgios Amanakis
2017-11-29 4:01 ` Dave Taht
2017-11-29 14:34 ` Georgios Amanakis
2017-11-29 14:43 ` Georgios Amanakis
2017-11-29 14:50 ` Toke Høiland-Jørgensen
2017-11-29 15:33 ` Pete Heist
2017-11-29 15:44 ` Toke Høiland-Jørgensen
2017-11-29 16:06 ` Georgios Amanakis
2017-11-29 17:44 ` Dave Taht
2017-11-29 17:49 ` Georgios Amanakis
[not found] ` <CACvFP_hJJNJh98Eu30zEYQO5jW6CwQcxK-FBYMuOi796FwkOww@mail.gmail.com>
2017-11-29 17:51 ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 18:00 ` Dave Taht
2017-11-29 18:19 ` Georgios Amanakis [this message]
2017-11-29 18:51 ` Dave Taht
2017-11-29 18:54 ` Georgios Amanakis
2017-11-29 20:06 ` Dave Taht
[not found] ` <CACvFP_iG1tTJLbpsd7YCQRH=TKX5rz4GZ8m1x34xGahSTWTgzA@mail.gmail.com>
2017-11-29 20:38 ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 21:04 ` [Cake] " Georgios Amanakis
2017-11-30 17:54 ` Dave Taht
2017-11-29 17:54 ` [Cake] " Dave Taht
[not found] ` <CACvFP_jkqS4b1w7sfNDthx4G4_fp21P-DDFtREGMzz+zLzcThQ@mail.gmail.com>
2017-11-29 17:59 ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 16:08 ` [Cake] " Pete Heist
2017-11-29 16:12 ` Georgios Amanakis
2017-11-29 16:17 ` Toke Høiland-Jørgensen
2017-11-29 16:21 ` Toke Høiland-Jørgensen
2017-11-29 16:24 ` Georgios Amanakis
2017-11-29 16:27 ` Pete Heist
2017-11-29 16:36 ` Georgios Amanakis
2017-11-29 16:40 ` Toke Høiland-Jørgensen
[not found] ` <CACvFP_g66TUdpVtFuJOi_5E1XVCf1Fo1QuRf5zG4nGDExWE2JA@mail.gmail.com>
2017-11-29 16:55 ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 3:42 ` [Cake] " Georgios Amanakis
2017-11-29 8:19 ` Pete Heist
2017-11-29 12:07 ` 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='CACvFP_jwqVj4ZT1=ji4LeQn9R723tycjGYPyLAzqKXdMEKPz3w@mail.gmail.com' \
--to=gamanakis@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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