From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] sce ramp vs threshold
Date: Thu, 8 Aug 2019 09:17:21 -0700 [thread overview]
Message-ID: <CAA93jw6RAfsnL0yfq1J_zewrVHvR9QNYG7Yk_KGnDxtsS1oX9w@mail.gmail.com> (raw)
My original understanding of sce was that a threshold function
sufficed for fq, and a ramp was needed for
single queues. Is that still the case?
I *reallly* want to see the cpu overhead of this stuff on cheap
hardware, so I'm fiddling with this:
https://github.com/dtaht/fq_codel_fast/commit/9e6ab76c81fd26f22806f19476481a1b92c9703e
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-08-08 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 16:17 Dave Taht [this message]
2019-08-08 17:50 ` Jonathan Morton
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6RAfsnL0yfq1J_zewrVHvR9QNYG7Yk_KGnDxtsS1oX9w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ecn-sane@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