From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] strict(er) priority model
Date: Thu, 19 Nov 2015 10:22:45 +0100 [thread overview]
Message-ID: <CAA93jw6mEGMm7BQbkQPfAMJZ93rakX5pfi7PiDdWQ_iBxTb1gg@mail.gmail.com> (raw)
There are a few circumstances where the inherent bandwidth/latency
tradeoffs in cake are trumped by perceived needs for strict priority
queues.
One fairly common one is on boxes doing bgp, where the bgp flow "must"
complete as fast as possible. There are probably other cases in the
network routing world (how does ISIS exchange routes? ospf?)
A common case for voip-ers is to strictly prioritize udp sip/rtp flows
over everything else.
Having a model available closer in implementation (and NOT the
default) to the strict priority queues sch_fq and pfifo_fast have may
ease adoption. ?
then there are vlans and so on...
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
next reply other threads:[~2015-11-19 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:22 Dave Taht [this message]
2015-11-19 23:54 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6mEGMm7BQbkQPfAMJZ93rakX5pfi7PiDdWQ_iBxTb1gg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@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