From: Toerless Eckert <tte@cs.fau.de>
To: rpm@lists.bufferbloat.net
Subject: [Rpm] Test procedures for TCP stacks ?
Date: Mon, 31 Jan 2022 16:27:36 +0100 [thread overview]
Message-ID: <Yff/6L3gS4+qgOlx@faui48e.informatik.uni-erlangen.de> (raw)
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
next reply other threads:[~2022-01-31 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:27 Toerless Eckert [this message]
2022-02-01 17:29 ` Christoph Paasch
2022-02-01 19:19 ` Dave Taht
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=Yff/6L3gS4+qgOlx@faui48e.informatik.uni-erlangen.de \
--to=tte@cs.fau.de \
--cc=rpm@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