From: Dave Taht <dave.taht@gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] Test procedures for TCP stacks ?
Date: Tue, 1 Feb 2022 11:19:04 -0800 [thread overview]
Message-ID: <CAA93jw66MmAp2EgWjMe0vBn=OuJ6L2ZkzEDQZvpvqFBGsNwXJw@mail.gmail.com> (raw)
In-Reply-To: <Yff/6L3gS4+qgOlx@faui48e.informatik.uni-erlangen.de>
"Quality" is an attribute I think about based on Deming's work on TQM,
and Zen and the Art of Motorcycle Maintenance.
You know it when you see it, feel it, taste it, hold its heft in your
hand, and wheel your bike out of the garage after a long winter and it
starts right up.
On Mon, Jan 31, 2022 at 7:27 AM Toerless Eckert via Rpm
<rpm@lists.bufferbloat.net> wrote:
>
> Are thre any well defined (RFC or the like) test procedures for the "quality"
> of TCP stacks ? I am especially thinking about measuring how good the
> TCP stack behaves in the face of various path problems. Latency, loss,
> reorder,.
>
> Related:
>
> How big a difference between goodput and throughput would one be able to
> see anyhow between worst... best TCP stacks ?
>
> Thanks!
> Toerless
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
prev parent reply other threads:[~2022-02-01 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:27 Toerless Eckert
2022-02-01 17:29 ` Christoph Paasch
2022-02-01 19:19 ` Dave Taht [this message]
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw66MmAp2EgWjMe0vBn=OuJ6L2ZkzEDQZvpvqFBGsNwXJw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=rpm@lists.bufferbloat.net \
--cc=tte@cs.fau.de \
/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