From: Aaron Wood <woody77@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] QoS and test setups
Date: Thu, 5 May 2016 19:08:46 -0700 [thread overview]
Message-ID: <CALQXh-PXc=eR7mbgkCS0gGq8z578Zii0g1-jCbRnqNhoe+uDQA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
I saw Dave's tests on WMM vs. without, and started thinking about test
setups for systems when QoS is in use (using classification, not just
SQM/AQM).
There are a LOT of assumptions made when QoS systems based on marked
packets is used:
- That traffic X can starve others
- That traffic X is more/most important
Our test tools are not particularly good at anything other than hammering
the network (UDP or TCP). At least TCP has a built-in congestion control.
I've seen many UDP (or even raw IP) test setups that didn't look anything
like "real" traffic.
I know Dave has wanted an isochronous traffic tool that could simulate voip
traffic (with in-band one-way latency/jitter/loss measurement
capabilities).
What other tools do we need, for replicating traffic types that match how
these QoS types in wifi are meant to be used? I think we're doing an
excellent job of showing how they can be abused. Abusing is pretty easy,
at this point (rrul, iPerf, etc).
-Aaron Wood
[-- Attachment #2: Type: text/html, Size: 1189 bytes --]
next reply other threads:[~2016-05-06 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 2:08 Aaron Wood [this message]
2016-05-06 2:24 ` Bob McMahon
2016-05-06 4:41 ` Jonathan Morton
2016-05-07 16:50 ` Dave Taht
2016-05-07 21:49 ` Dave Taht
2016-05-08 19:07 ` Bob McMahon
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='CALQXh-PXc=eR7mbgkCS0gGq8z578Zii0g1-jCbRnqNhoe+uDQA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.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