Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] documentation review request and out of tree cake builds for openwrt/etc.
Date: Thu, 30 Apr 2015 17:52:42 +0300	[thread overview]
Message-ID: <CAJq5cE3FeXnnvYY1pr9Emi3QGOjpM+CUy-_eumn_Uocq2o5oxA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4ax3c+Ak7Rn4zvzZPFJWu6V5HL3q8Nx2vUvfBvXOM4Pg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

I'm not concerned about aggregation effects on cable, because it's not
station specific as it is on Wi-Fi. It might be a source of one extra
access grant delay at most; after that there'll be enough packets in the
modem's FIFO to justify a full sized grant. Here the modem's buffer really
does exist for a good reason, and we can rely on it to do the job.

I'm also not concerned about ack bunching, because realistically that isn't
really caused by FQ. Given a 10:1 bandwidth ratio, and a 3:1 delayed ack
factor, there'll be 3.33 acks for each data packet in the slow direction,
while at our default 300 quantum the DRR will cycle five times per data
packet. So acks for a given flow will only be delivered bunched if they
arrived bunched.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 851 bytes --]

      parent reply	other threads:[~2015-04-30 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 18:04 [Cerowrt-devel] " Dave Taht
2015-04-28 20:52 ` [Cerowrt-devel] [Cake] " Jonathan Morton
2015-04-30  0:10   ` Dave Taht
2015-04-30 14:38     ` Jonathan Morton
2015-04-30 15:17       ` Dave Taht
2015-05-01  9:50         ` Kevin Darbyshire-Bryant
2015-05-01 11:06         ` Kevin Darbyshire-Bryant
2015-04-30 14:52     ` Jonathan Morton [this message]

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=CAJq5cE3FeXnnvYY1pr9Emi3QGOjpM+CUy-_eumn_Uocq2o5oxA@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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