Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@reed.com>
To: "Mike \"dave\" Taht" <dave.taht@gmail.com>,
	Erkki Lintunen <ebirdie@iki.fi>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] an option for a new platform?
Date: Sat, 13 Dec 2014 18:02:25 -0500	[thread overview]
Message-ID: <f11574e3-f848-475d-9d26-9c1f00b4b8ee@reed.com> (raw)
In-Reply-To: <CAA93jw63tNVYanzYHkUxST2pr=x6ZsCJWcabgpLibA10iCk85g@mail.gmail.com>

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

Anyone measured what is the actual bottleneck in 300 mb/s shaping?  On an Intel platform you can measure a running piece of code pretty accurately. I ask because it is not obvious a cpu needs to touch much of a frame to do shaping, so it seems more likely that the driver and memory management structures are the bottleneck.

But it is really easy to write very slow code in a machine with limited cache. So maybe that is it.

On a multi core intel arch machine these days it is a surprising fact that a single core can't use up more than about 25 percent of  a socket's memory cycles so to get full i/o speed you need to be running your code on 4 cores or more... this kind of thing can really limit achievable speed of a poorly threaded design.  Architectural optimization needs more than llvm and clean code. You need to think about the whole software pipeline. Debian may not be great out of the box for this reason - it was never designed for routing throughput.

On Dec 12, 2014, Dave Taht <dave.taht@gmail.com> wrote:
>There was a review of that hardware that showed it couldn't push more
>than 600Mbit natively (without shaping). I felt that the ethernet
>driver could be improved significantly after looking it over, but
>didn't care for the 600mbit as a starting point to have to improve
>from.
>
>Not ruling it out, though! It met quite a few requirements we have.
>
>On Thu, Dec 11, 2014 at 11:33 PM, Erkki Lintunen <ebirdie@iki.fi>
>wrote:
>>
>> Hello,
>>
>> while enjoying and reading another thread from the list...
>>
>>> -------- Forwarded Message --------
>>> Subject: Re: [Cerowrt-devel] how is everyone's uptime?
>>> Date: Thu, 11 Dec 2014 16:42:37 -0800
>>> From: Dave Taht <dave.taht@gmail.com>
>> [snip]
>>> But frankly, I would prefer for most of the chaos there to subside
>and to find
>>> a new, additional platform, to be working on before resuming work,
>>> that can do inbound shaping at up to 300mbit. And
>>> to be more openwrt compatible in whatever we do, whatever that is.
>>
>> this reminded me that another day I passed a web-page of a platform
>and
>> in the hope this has not been on the list yet passing it forward.
>>
>> <http://www.pcengines.ch/apu.htm>
>>
>> An interesting tidbit in the platform is the choice of firmware, I
>> think. Haven't seen any board yet with the similar choice by the
>> manufacturer. With a quick summing from the vendor part catalog, the
>> platform is sub 200 EUR (238 USD in current exchange rate) for an
>about
>> working assembly of 3x 1GbE, 4G ram, 1G flash, 802.11a/b/g/n radio...
>>
>> I can't say anything how capable the hw might be for the stated
>inbound
>> shaping performance. I have had an ALIX board from their previous
>> generation for years and its been humming nicely though I haven't
>pushed
>> it to its envelope.
>>
>> Best
>> Erkki
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
>--
>Dave Täht
>
>thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

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

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

  reply	other threads:[~2014-12-13 23:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 22:52 [Cerowrt-devel] how is everyone's uptime? Dave Taht
2014-12-11 19:58 ` Valdis.Kletnieks
2014-12-11 21:50   ` Dave Taht
2014-12-12  0:18     ` Valdis.Kletnieks
2014-12-12  0:22       ` Dave Taht
2014-12-12  0:32 ` Aaron Wood
2014-12-12  0:42   ` Dave Taht
2014-12-12  7:33     ` [Cerowrt-devel] an option for a new platform? Erkki Lintunen
2014-12-12 14:52       ` Dave Taht
2014-12-13 23:02         ` David P. Reed [this message]
2014-12-16  9:02           ` Dave Taht
2014-12-12  1:30 ` [Cerowrt-devel] how is everyone's uptime? Joseph Swick
2014-12-12  1:52 ` Jim Gettys

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=f11574e3-f848-475d-9d26-9c1f00b4b8ee@reed.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ebirdie@iki.fi \
    /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