Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Master branch updated
Date: Tue, 4 Oct 2016 10:46:16 +0200	[thread overview]
Message-ID: <66438228-D13A-42C4-8B42-11C49E0B2587@gmx.de> (raw)
In-Reply-To: <F40C99D0-524A-49BC-B833-C8DB23270603@gmail.com>

Hi Jonathan,

> On Oct 4, 2016, at 09:22 , Jonathan Morton <chromatix99@gmail.com> wrote:
> 
> I’ve just merged the NAT, PTM

	About that PTM accounting, could you explain why you want to perform the adjustment as a a “virtual” size increase per packet instead of a “virtual” rate reduction? The arguments for adjusting the rate are as follows:
1) You only need to adjust the rate if the rate was changed compared to for each packet, which should save CPU time and be more efficient.

2) For most users the rate (potentially expressed as bits per second) will be larger than the typical packet size (around 1540 Bytes) so adjusting the rate should introduce less rounding imprecision. To put this in numbers 1540 Byte equal 12.32 Kbit.

I am confident that you have good reasons for you implementation decisions, all I want is to learn what those are.

Best Regards
	Sebastian

P.S.: I realize that I am  looking like  a one-trick pony totally hung up on the overhead adjustment issue. I would prefer to let go, but I want to be certain that this is in good hands before I do this, as the value of doing these compensations IMHO depends on absolute meticulous attention (so needs any additional pair of eyes to peer over it).



> and Linux-4.8 compatibility stuff into the master branch of Cake.  It’s stable code and a definite improvement.
> 
> This frees up the Cobalt branch for more experimentation, such as the rewrite of triple-isolate that I also just pushed.  I found a way to make it more DRR-like, by simply scaling down the quantum used for each host by the number of flows attached to that host.
> 
> I still need to test whether it works as well as the old version, but it should at least be less CPU intensive.  In particular it should no longer require bursts of CPU activity when the host deficits expire, and host deficit expiry should no longer be explicitly synchronised.
> 
> See if, between you, you can break it before I get back from shopping.  :-)
> 
> - Jonathan Morton
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  reply	other threads:[~2016-10-04  8:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04  7:22 Jonathan Morton
2016-10-04  8:46 ` moeller0 [this message]
2016-10-04 11:18   ` Jonathan Morton
2016-10-04 11:54     ` moeller0
2016-10-04 16:23       ` Loganaden Velvindron
2016-10-04 15:22 ` Kevin Darbyshire-Bryant
2016-10-04 16:28   ` Jonathan Morton
2016-10-11  5:41     ` Jonathan Morton
2016-10-11 12:09       ` Luis E. Garcia

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=66438228-D13A-42C4-8B42-11C49E0B2587@gmx.de \
    --to=moeller0@gmx.de \
    --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