From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Make-wifi-fast] [Starlink] bloat on wifi8 and 802.11 wg
Date: Mon, 2 Sep 2024 19:22:22 -0400 [thread overview]
Message-ID: <88f9319e-0710-417c-9c73-079bc90e45e9@rogers.com> (raw)
In-Reply-To: <20240902042024.8A7E3620054@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On 9/2/24 00:20, Hal Murray via Bloat wrote
> What does that say about the minimal collection of gear required in a test
> lab?
>
> If you had a lab with plenty of gear, what tests would you run?
>
> How many different tests would it take to give reasonable coverage?
>
This is called "the modem testing problem" (:-)) The usual answers are
1. just my own brand
2. the most popular, plus mine
That slowly leads to a series of failures in the industry, followed by
lots of mergers and acquisitions.
If one has a collection of hardware that have APIs, and a testing
mechanism that's also programmable, then you can do /line coverage by
exhaustion/, identify the failing configurations Given a list of failing
combinations, you can set up tests for just them to run more often.
As it's name suggests, the main test can take a while (:-))
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 1747 bytes --]
next prev parent reply other threads:[~2024-09-02 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 15:28 [Bloat] WiFi Livingood, Jason
2024-05-08 15:35 ` [Bloat] bloat on wifi8 and 802.11 wg Dave Taht
2024-05-08 21:18 ` Dorothy Stanley
2024-05-08 21:22 ` Dorothy Stanley
2024-09-02 1:15 ` [Bloat] [Make-wifi-fast] " Bob McMahon
2024-09-02 2:59 ` [Bloat] [Starlink] " David Lang
2024-09-02 4:20 ` [Bloat] [Make-wifi-fast] [Starlink] " Hal Murray
2024-09-02 5:05 ` David Lang
2024-09-02 15:04 ` [Bloat] Real-world testing: " Rich Brown
2024-09-02 15:09 ` [Bloat] [Make-wifi-fast] " Sebastian Moeller
2024-09-02 15:37 ` David Lang
2024-09-02 17:28 ` [Bloat] [Make-wifi-fast] [Starlink] bloat on " Bob McMahon
2024-09-02 17:31 ` Frantisek Borsik
2024-09-02 18:02 ` Bob McMahon
2024-09-03 3:20 ` David Lang
2024-09-03 15:42 ` Bob McMahon
2024-09-02 23:22 ` David Collier-Brown [this message]
2024-09-02 12:09 ` [Bloat] [Starlink] [Make-wifi-fast] " Michael Richardson
2024-09-02 16:37 ` Brandon Butterworth
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88f9319e-0710-417c-9c73-079bc90e45e9@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@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