From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] Measuring CoDel
Date: Fri, 22 Jan 2021 15:37:10 -0800 [thread overview]
Message-ID: <20210122233710.1B911406061@ip-64-139-1-69.sjc.megapath.net> (raw)
Toke said:
> Yeah, the overhead of CoDel itself (and even FQ-CoDel) is basically nil (as
> in, we have not been able to measure it), when otherwise doing forwarding
> using the regular Linux stack.
I may be able to help with that.
Are you familiar with Dick Sites' KUtrace?
Stanford Seminar - KUtrace 2020
https://www.youtube.com/watch?v=2HE7tSZGna0
The catch is that I've never used CoDel so somebody will have to teach me how
to setup a test environment, and then show me the chunks in the kernel you
want to measure.
--
These are my opinions. I hate spam.
next reply other threads:[~2021-01-22 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 23:37 Hal Murray [this message]
2021-01-23 0:34 ` Toke Høiland-Jørgensen
2021-01-25 9:31 ` Jesper Dangaard Brouer
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=20210122233710.1B911406061@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@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