From: David Lang <david@lang.hm>
To: Michael Menth <menth@uni-tuebingen.de>
Cc: "Jesper Dangaard Brouer" <jbrouer@redhat.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Up-to-date buffer sizes?
Date: Wed, 9 Mar 2022 10:06:17 -0800 (PST) [thread overview]
Message-ID: <3oq1pps-7sp1-4q54-5n8s-nq4p667923sn@ynat.uz> (raw)
In-Reply-To: <5a8b6b4a-7f15-3f08-56b5-9e04773271bb@uni-tuebingen.de>
[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]
If the link is not a bottleneck, then you will not be using buffers (whatever
they are configured to be)
networking gear tends toward the proprietary (although there's a growing amount
that's linux based now) and they tend to be very closed mouth about
configuration like this.
David Lang
On Wed, 9 Mar 2022, Michael Menth wrote:
> Date: Wed, 9 Mar 2022 18:39:08 +0100
> From: Michael Menth <menth@uni-tuebingen.de>
> To: Jesper Dangaard Brouer <jbrouer@redhat.com>,
> Toke Høiland-Jørgensen <toke@toke.dk>, bloat <bloat@lists.bufferbloat.net>
> Subject: Re: [Bloat] Up-to-date buffer sizes?
>
> Hi all,
>
> I don't question the usefulness of AQMs for buffers - on the contrary.
> But what are up-to-date buffer sizes in networking gears, especially if
> AQMs are not in use? It's hard to find public and information about it.
> Anyone can point to a citable source?
>
> This raises also the question about the deployment of AQMs in networking
> infrastructure. I know it's already adopted by some OSs, but what about
> forwarding nodes? Any papers about it?
>
> Kind regards
>
> Michael
>
> Am 09.03.2022 um 18:24 schrieb Jesper Dangaard Brouer:
>>
>>
>> On 09/03/2022 17.31, Toke Høiland-Jørgensen via Bloat wrote:
>>> 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... :)
>>
>> Exactly, I agree with Toke. The important parameter is the latency.
>> Or the packet sojourn time (rfc8289 + rfc8290) observed waiting in the
>> queue.
>>
>> The question you should be asking is:
>> - What is the max queue latency I'm "willing" to experience on this link?
>>
>> Hint, you can then depending on the link rate calculate the max buffer
>> size you should configure.
>>
>> The short solution is:
>> - just use fq_codel (rfc8290) as the default qdisc.
>>
>> --Jesper
>>
>>
>>
>
>
next prev parent reply other threads:[~2022-03-09 18:06 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
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 [this message]
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=3oq1pps-7sp1-4q54-5n8s-nq4p667923sn@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=jbrouer@redhat.com \
--cc=menth@uni-tuebingen.de \
--cc=toke@toke.dk \
/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