From: Dave Taht <dave@taht.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] [RFC PATCH 2/3] Add cake related includes and source files
Date: Tue, 21 Nov 2017 11:04:29 -0800 [thread overview]
Message-ID: <87po8btpvm.fsf@nemesis.taht.net> (raw)
In-Reply-To: <f7a57f62-9b61-5e4f-6734-dc92f2758d2f@gmail.com> (Jonathan Morton's message of "Tue, 21 Nov 2017 00:21:30 +0200")
Jonathan Morton <chromatix99@gmail.com> writes:
> On 17/11/17 21:52, Dave Taht wrote:
>>> + schedule = now - vars->drop_next;
>
>> I don't understand the schedule concept that well. Kind of goes with not
>> understanding the overloading of the drop_next field.
>
> The 'schedule' variable simply records, in its sign, whether 'now' is before or
> after 'drop_next'. This allows 'drop_next' to be updated before the next
> scheduling decision is actually branched, without destroying that information.
> Similarly, the first 'schedule' value calculated is preserved in the boolean
> 'next_due'.
>
> As for 'drop_next', I'm simply taking advantage of the fact that 'interval' is
> both the delay between first exceeding 'target' and the first signalling event,
> *and* the scaling factor for the signalling frequency. It's therefore very
> natural to use a single mechanism for both purposes, and eliminates a
> significant amount of reference Codel's spaghetti code. To help with this, both
> the '0' and '1' entries in the invsqrt cache are 0xFFFFFFFF, as close as
> possible to 1.0 in fixed-point.
These are worthy comments to have in the code.
next prev parent reply other threads:[~2017-11-21 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 19:11 [Cake] [RFC PATCH 0/3] Cake patches for net-next Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 1/3] Add cake to pkt_sched.h Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 2/3] Add cake related includes and source files Dave Taht
2017-11-17 19:52 ` Dave Taht
[not found] ` <91830311-fea3-cb03-be2e-b132ae54ad89@gmail.com>
2017-11-21 18:59 ` Dave Taht
[not found] ` <dbf49d41-27e1-5d4c-ad23-093d3d2d442e@gmail.com>
2017-11-21 19:03 ` Dave Taht
[not found] ` <f7a57f62-9b61-5e4f-6734-dc92f2758d2f@gmail.com>
2017-11-21 19:04 ` Dave Taht [this message]
[not found] ` <fe13b27c-223f-f9d2-b153-44fbe388ff50@gmail.com>
2017-11-21 19:05 ` Dave Taht
[not found] ` <5fbd8b62-f557-d9f6-0396-8bd9135b7c74@gmail.com>
2017-11-21 19:07 ` Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 3/3] Add support for building the new cake qdisc Dave Taht
2017-11-17 19:21 ` Toke Høiland-Jørgensen
2017-11-17 19:55 ` Dave Taht
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=87po8btpvm.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=cake@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