From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Tim Higgins <tim@smallnetbuilder.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Cc: flent-users@flent.org
Subject: Re: [Make-wifi-fast] Flent traffic direction convention
Date: Fri, 27 Mar 2020 12:05:10 +0100 [thread overview]
Message-ID: <87r1xem521.fsf@toke.dk> (raw)
In-Reply-To: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com>
(Adding flent-users@flent.org - please also include this in
Flent-specific questions)
> I might be confusing myself, but need to ask the question. What does flent
> define as upload and download?
>
> Netperf docs say:
> The TCP_STREAM test is the default test in netperf. It is quite simple,
> transferring some quantity of data from the system running netperf to the
> system running netserver.
>
> So why, when I look at tcp_1up_noping.conf does the DATA_SETS have 'test':
> 'TCP_STREAM' in the 'TCP_upload' dictionary?
Flent considers itself the client, so 'upload' is TCP_STREAM. As more
use cases have emerged, this has turned out to not always be the case,
of course; WiFi test scenarios such as you are doing being the most
prominent example. There's a --swap-up-down parameter which will switch
all instances of TCP_STREAM to TCP_MAERTS and vice-versa, though.
> Second question: Is there any documentation that can help me figure out
> exactly what traffic is running in each test type?
> I've tried looking at the .conf and .inc files, in flent/tests but can't
> figure it out.
Not really :/ There's https://flent.org/tests.html, but it hasn't really
kept up with new tests being added.
However, you can see it after the fact: The exact command lines for each
data series is stored (along with a bunch of other data) in the
SERIES_META object in the data file. Use the GUI to browse this, or
print it with 'flent -f metadata datafile.flent.gz'.
-Toke
next prev parent reply other threads:[~2020-03-27 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 21:22 Tim Higgins
2020-03-27 11:05 ` Toke Høiland-Jørgensen [this message]
2020-03-27 11:31 ` Tim Higgins
2020-03-27 12:28 ` [Make-wifi-fast] [Flent-users] " Toke Høiland-Jørgensen
2020-03-31 13:48 ` [Make-wifi-fast] " Erkki Lintunen
2020-03-31 13:59 ` Tim Higgins
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1xem521.fsf@toke.dk \
--to=toke@redhat.com \
--cc=flent-users@flent.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=tim@smallnetbuilder.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