From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Michael Menth <menth@uni-tuebingen.de>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Up-to-date buffer sizes?
Date: Wed, 09 Mar 2022 17:31:41 +0100 [thread overview]
Message-ID: <87y21julxu.fsf@toke.dk> (raw)
In-Reply-To: <d3860259-ddd7-c9c7-d8d5-6939e52f8c1b@uni-tuebingen.de>
Michael Menth <menth@uni-tuebingen.de> writes:
> Hi all,
>
> are there up-to-date references giving evidence about typical buffer
> sizes for various link speeds and technologies?
Heh. There was a whole workshop on it a couple of years ago; not sure if
it concluded anything: http://buffer-workshop.stanford.edu/program/
But really, asking about buffer sizing is missing the point; if you have
static buffers with no other management (like AQM and FQ) you're most
likely already doing it wrong... :)
-Toke
next prev parent reply other threads:[~2022-03-09 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:22 Michael Menth
2022-03-09 16:31 ` Toke Høiland-Jørgensen [this message]
2022-03-09 17:24 ` Jesper Dangaard Brouer
2022-03-09 17:39 ` Michael Menth
2022-03-09 17:51 ` Aaron Wood
2022-03-09 18:06 ` David Lang
2022-03-10 8:01 ` Jonas Mårtensson
2022-03-09 18:15 ` Amr Rizk
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=87y21julxu.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=menth@uni-tuebingen.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