From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] archer c7 v2, policing, hostapd, test openwrt build
Date: Sun, 22 Mar 2015 18:45:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1503221844590.22474@nftneq.ynat.uz> (raw)
In-Reply-To: <08BAF198-87C5-42B8-8899-53F34E47156E@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1228 bytes --]
On Mon, 23 Mar 2015, Jonathan Morton wrote:
>> On 23 Mar, 2015, at 02:24, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I have long maintained it was possible to build a better fq_codel-like
>> policer without doing htb rate shaping, ("bobbie"), and I am tempted
>> to give it a go in the coming months.
>
> I have a hazy picture in my mind, now, of how it could be made to work.
>
> A policer doesn’t actually maintain a queue, but it is possible to calculate when the currently-arriving packet would be scheduled for sending if a shaped FIFO was present, in much the same way that cake actually performs such scheduling at the head of a real queue. The difference between that time and the current time is a virtual sojourn time which can be fed into the Codel algorithm. Then, when Codel says to drop a packet, you do so.
>
> Because there’s no queue management, timer interrupts nor flow segregation, the overhead should be significantly lower than an actual queue. And there’s a reasonable hope that involving Codel will give better results than either a brick-wall or a token bucket.
are we running into performance issues with fq_codel? I thought all the problems
were with HTB or ingress shaping.
David Lang
next prev parent reply other threads:[~2015-03-23 1:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 0:24 Dave Taht
2015-03-23 0:31 ` Jonathan Morton
2015-03-23 1:10 ` Jonathan Morton
2015-03-23 1:18 ` Dave Taht
2015-03-23 1:34 ` Jonathan Morton
2015-03-23 1:45 ` David Lang [this message]
2015-03-23 2:00 ` Dave Taht
2015-03-23 2:10 ` Jonathan Morton
2015-03-23 2:15 ` Dave Taht
2015-03-23 2:18 ` Dave Taht
2015-03-23 6:09 ` Sebastian Moeller
2015-03-23 13:43 ` Jonathan Morton
2015-03-23 16:09 ` Sebastian Moeller
2015-03-24 0:00 ` Sebastian Moeller
2015-03-24 0:05 ` Dave Taht
2015-03-24 0:07 ` Sebastian Moeller
2015-03-24 3:16 ` Jonathan Morton
2015-03-24 7:47 ` Sebastian Moeller
2015-03-24 8:13 ` Jonathan Morton
2015-03-24 8:46 ` Sebastian Moeller
2015-03-29 1:14 ` Sebastian Moeller
2015-03-29 6:17 ` Jonathan Morton
2015-03-29 11:16 ` Sebastian Moeller
2015-03-29 12:48 ` Jonathan Morton
2015-03-29 14:16 ` Sebastian Moeller
2015-03-29 15:13 ` Jonathan Morton
2015-03-23 17:08 ` David Lang
2015-03-23 16:17 ` Sebastian Moeller
2015-03-23 16:27 ` Dave Taht
2015-03-23 17:07 ` David Lang
2015-03-23 18:16 ` 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/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=alpine.DEB.2.02.1503221844590.22474@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@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