From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Cc: s.aoyagi@chiba-u.jp, yuuki-ho@chiba-u.jp,
sekiya@faculty.chiba-u.jp, hiendtt@uit.edu.vn,
thanhnd@uit.edu.vn, duyld@uit.edu.vn,
Kien NGUYEN <nguyen@chiba-u.jp>
Subject: [Make-wifi-fast] An "Accurate" Platform for Investigating TCP Performance in Wi-Fi Networks
Date: Wed, 19 Jul 2023 18:30:06 -0600 [thread overview]
Message-ID: <CAA93jw7dnpo+Pz43izNQjyij0+3OZhFjxisf5zb0GKcrq90XdQ@mail.gmail.com> (raw)
It is hard to contain my disappointment that a modern work on wifi,
that even mentions bufferbloat, could have missed our work on fixing
wifi (such as "ending the anomaly", now the default APIs in the linux
kernel), and make claims for the emulator that are so completely
wrong, and further claim that the behaviors matched a real world AP.
re: https://mdpi-res.com/d_attachment/futureinternet/futureinternet-15-00246/article_deploy/futureinternet-15-00246.pdf?version=1689771540
Can I suggest strongly to the authors that they try to understand rate
vs range vs buffering, the intersection of the half duplex txop
infrastructure with multiple stations, the side effects of
aggregation, and other scheduling difficulties mininet does not come
even close to handling?
20 packet buffers?? A more typical number is much greater.
Test through walls or at distance?
Here are 4 resources that might help deepen your understanding.
https://www.youtube.com/watch?v=Rb-UnHDw02o&t=1532s (10 minutes here,
but do the whole thing)
https://bufferbloat-and-beyond.net/
https://www.cs.kau.se/tohojo/airtime-fairness/
https://blog.cerowrt.org/post/minstrel/
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
next reply other threads:[~2023-07-20 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 0:30 Dave Taht [this message]
2023-07-20 0:48 ` Bob McMahon
2023-07-20 1:54 ` Dave Taht
2023-07-20 2: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=CAA93jw7dnpo+Pz43izNQjyij0+3OZhFjxisf5zb0GKcrq90XdQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=duyld@uit.edu.vn \
--cc=hiendtt@uit.edu.vn \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nguyen@chiba-u.jp \
--cc=s.aoyagi@chiba-u.jp \
--cc=sekiya@faculty.chiba-u.jp \
--cc=thanhnd@uit.edu.vn \
--cc=yuuki-ho@chiba-u.jp \
/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