From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake flenter results round 0
Date: Sun, 26 Nov 2017 10:47:30 +0100 [thread overview]
Message-ID: <8F179D16-9E10-44B3-B84C-8A988DD376F5@gmail.com> (raw)
In-Reply-To: <CAA93jw5dU4PZ71U7Se5hcnTB=KpO-YjZsFgT+k9RUTzqOw-nnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
> On Nov 26, 2017, at 9:42 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> That is a really, really long, and extremely pleasant, way of saying:
>
> "OK, it doesn't crash".
>
> :)
>
> can flenter work with the veth stuff and namespaces?
Maybe a little more than that, but not much more. :) I put it on git for reference: https://github.com/peteheist/flenter <https://github.com/peteheist/flenter>
So far no to the veth and namespace support, but I don’t see why it couldn’t. A flenter “rig" includes up to six roles. In this test I’m only using four since it’s not over p2p wifi: client, client router, server router and server. The script doesn’t care where those are as long as it can ssh to them without a password so it can run flenter_shell.sh to do its setup and run flent on the client. My dream was that you could just define your rig with a few parameters, run it, and enjoy all the results. That dream is still more of a waking nightmare as you have to modify the tests based on what your rig can do.
I think the most important thing to making the tests more relevant for cake after "round 1” changes is using different bandwidths and rtts, right? I could use netem for this. The use of veth and namespaces is mainly for getting it to run on one box, right? Where’s the latest code for that, btw? I’m a little lost as to whether or if I need to be using net-next, if I can just use the current netem I have, where to get the latest netem and veth / namespaces stuff, etc...
[-- Attachment #2: Type: text/html, Size: 2199 bytes --]
next prev parent reply other threads:[~2017-11-26 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 8:12 Pete Heist
2017-11-26 8:42 ` Dave Taht
2017-11-26 9:47 ` Pete Heist [this message]
2017-11-26 17:45 ` Dave Taht
2017-11-26 18:59 ` Pete Heist
2017-11-26 18:19 ` Dave Taht
2017-11-26 19:18 ` 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=8F179D16-9E10-44B3-B84C-8A988DD376F5@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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