Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Iain R. Learmonth" <irl@fsfe.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Packet Pacing
Date: Mon, 24 Feb 2014 11:55:17 -0500	[thread overview]
Message-ID: <CAA93jw4qZ23KaQAUXVvrxjLXJXC-rUJdjVP9D28VtmzynSTzcw@mail.gmail.com> (raw)
In-Reply-To: <530B6186.1070509@fsfe.org>

On Mon, Feb 24, 2014 at 10:13 AM, Iain R. Learmonth <irl@fsfe.org> wrote:
> Sup,
>
> I am attempting to perform some measurements using CoDel, PIE and
> DropTail using the CeroWRT platform but the rate-limiting appears to be
> happening before the queuing. The problem here is that there's no
> bottleneck between the queue and the output and so the AQM isn't really
> doing anything.

Huh? The SQM system creates a bottleneck and then various selectable AQM
technologies manage the queue in front, which is exactly what you want.

Note: In terms of strict pacing, the htb rate limiter system uses an increasing
quantum size to release bigger bursts of packets as we go to higher speeds.
(I think it starts increasing the quantum > MTU at about 20Mbit) -
this is because
the cpu scheduler can't effectively deliver single packets and still be useful
for other stuff.

see /usr/lib/sqm/ for details... or the gui...

If instead you want to run at line rate (10 or 100Mbit) there is
ethtool for that.

>
> I'd like to pace packets being dequeued to allow for the creation of a
> bottleneck where the output is the same link speed as the upstream link.

You can do this in multiple ways.


> Any ideas?
>
> Thanks,
> Iain.
>
> --
> urn:x-human:Iain R. Learmonth
> http://iain.learmonth.me/
> mailto:irl@fsfe.org
> xmpp:irl@jabber.fsfe.org
> tel:+447875886930
>
> GPG Fingerprint: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49
> Please verify out-of-band before trusting with sensitive information.
>
> [[[ To any GCHQ or other security service agents reading my email: ]]]
> [[[ Please consider if any professional body code of conduct to    ]]]
> [[[ which you subscribe requires you to follow Snowden's example.  ]]]
> [[[ Your professional membership, chartered or incorporated status ]]]
> [[[ may be at risk.                                                ]]]
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      reply	other threads:[~2014-02-24 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 15:13 Iain R. Learmonth
2014-02-24 16:55 ` Dave Taht [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=CAA93jw4qZ23KaQAUXVvrxjLXJXC-rUJdjVP9D28VtmzynSTzcw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=irl@fsfe.org \
    /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