Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>,David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] archer c7 v2, policing, hostapd, test openwrt build
Date: Mon, 23 Mar 2015 07:09:04 +0100	[thread overview]
Message-ID: <896FAE61-B45A-4F34-9449-5ADB82194DD9@gmx.de> (raw)
In-Reply-To: <D10FD962-461E-43DF-A45E-C4EAF8630685@gmail.com>

Hi Jonathan, hi Dave,

On March 23, 2015 3:10:52 AM GMT+01:00, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 23 Mar, 2015, at 03:45, David Lang <david@lang.hm> wrote:
>> 
>> are we running into performance issues with fq_codel? I thought all
>the problems were with HTB or ingress shaping.
>
>Cake is, in part, a response to the HTB problem; it is a few percent
>more efficient so far than an equivalent HTB+fq_codel combination.  It
>will have a few other novel features, too.
>
>Bobbie is a response to the ingress-shaping problem.  A policer (with
>no queue) can be run without involving an IFB device, which we believe
>has a large overhead.

        This is testable, if nobody beats me to it I will try this week. The main idea is to replace the ingress shaping on ge00 with egress shaping on the interface between the client and the router, so most likely se00 in cerowrt. This should effectively behave as the current sqm setup with ingress shaping, though only for hosts on se00. Of ifb truly is costly this setup should show better bandwidth use in rrul tests than the default. It obviously degrade local performance of se00 and hence be not a true solution unless one is happy to fully dedicate a box as shaper ;)

        Best Regards
                Sebastian


>
> - Jonathan Morton
>
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  parent reply	other threads:[~2015-03-23  6:09 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
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 [this message]
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=896FAE61-B45A-4F34-9449-5ADB82194DD9@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=david@lang.hm \
    /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