From: Sam Chessman <sam.chessman@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Linux Kernel network flow
Date: Wed, 6 Sep 2023 20:31:05 -0400 [thread overview]
Message-ID: <CAHMuPewojXjfe57Uvd9aBFH6HkGFZ5iaSEczDR7Y7XsY_iTtcA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
This effort appears to start with a bucket of clues:
https://github.com/leandromoreira/linux-network-performance-parameters
He references
https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/
I think he should be pointed to Flent.
[-- Attachment #2: Type: text/html, Size: 599 bytes --]
reply other threads:[~2023-09-07 0:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHMuPewojXjfe57Uvd9aBFH6HkGFZ5iaSEczDR7Y7XsY_iTtcA@mail.gmail.com \
--to=sam.chessman@gmail.com \
--cc=cerowrt-devel@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