General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>,
	Dave Taht via Bloat <bloat@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] temporal and spacial locality
Date: Mon, 26 Sep 2022 13:29:39 +0200	[thread overview]
Message-ID: <1AFEEC18-AE85-4C0D-8E78-8BAEE4359D11@gmx.de> (raw)
In-Reply-To: <CAA93jw77ESKF+g3PausroVpdSXKmbMTtv6s09VyGSAHMNMzOcw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

IMHO this is another example of 'batching helps to ameliorate per-batch set-up/processing costs'. The trick I would say is to size the batches in a way that they do not introduce too much latency granularity. For a server that might be a coarser granularity than for a client or a home router. My gut feeling tells me that the acceptable batch size is related to the required transmission/processing time of a batch.
In a sense cake already coarsely takes this into account when disabling GSO splitting at >= 1 Gbps rates. Maybe we could also scale the quantum more aggressively, but it is a tradeoff....


Regards

On 26 September 2022 03:19:30 CEST, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>Some good counterarguments against FQ and pacing.
>
>https://www.usenix.org/system/files/nsdi22-paper-ghasemirahni.pdf
>
>-- 
>FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
>Dave Täht CEO, TekLibre, LLC
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1728 bytes --]

      reply	other threads:[~2022-09-26 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  1:19 Dave Taht
2022-09-26 11:29 ` Sebastian Moeller [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/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=1AFEEC18-AE85-4C0D-8E78-8BAEE4359D11@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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