revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch@apple.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: rpm@lists.bufferbloat.net
Subject: Re: [Rpm] Test procedures for TCP stacks ?
Date: Tue, 01 Feb 2022 09:29:38 -0800	[thread overview]
Message-ID: <91CDABAF-5DD4-4233-9B73-320E57A506B3@apple.com> (raw)
In-Reply-To: <Yff/6L3gS4+qgOlx@faui48e.informatik.uni-erlangen.de>

Hello,

> On 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,.

I don't think that there is anything like that. All depends on what would be defined as "quality".

> 
> Related:
> 
> How big a difference between goodput and throughput would one be able to
> see anyhow between worst... best TCP stacks ?

That is interesting. It would be a measure of the efficiency of the TCP stack.


Christoph

> 
> Thanks!
>    Toerless
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm


  reply	other threads:[~2022-02-01 17:29 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 [this message]
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=91CDABAF-5DD4-4233-9B73-320E57A506B3@apple.com \
    --to=cpaasch@apple.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