[Cerowrt-devel] odroid C1+ status

[Cerowrt-devel] odroid C1+ status

[Dave Taht]

wow, thx for all the suggestions on alternate x86 router hardware... I
will read more later.

Would using a blog format for things like the following work better
for people? I could more easily revise, including graphics, etc,
etc... could try to hit on our hot buttons (upgradability, bloat,
reliability, kernel versions, manufacturer support) with some sort of
grading system...

http://the-edge.taht.net/post/odroid_c1_plus/ in this case

...

I got the odroid C1+ to work better. (either a cable or power supply
issue, I swapped both). On output it peaks at about 416Mbits with 26%
of cpu being spent in a softirq interrupt.  On input I can get it to
gbit, with 220% of cpu in use.

The rrul tests were pretty normal, aside from the apparent 400mbit
upload limit causing contention on rx/tx (at the moment I have no good
place to put these test results since snapon is now behind a firewall.
I'd like to get more organized about how we store and index these
results also)

There is no BQL support in the odroid driver for it, and it ships with
linux 3.10.80. At least its a LTS version.... I am totally unfamiliar
with the odroid ecosystem but maybe there is active kernel dev on it
somewhere?

(The pi 2, on the other hand, is kernel 4.1.17-v7 AND only has a
100mbit phy, so it is hard to complain about only getting 400mbit from
the odroid c1+, but, dang it, a much later kernel would be nice in the
odroid)

My goal in life, generally, is to have a set of boxes with known
characteristics to drive tests with, that are reliable enough to setup
once and ignore.

A) this time around, I definitely wanted variety, particularly in tcp
implementations, kernel versions, ethernet and wifi chips - as it
seemed like drawing conclusions from "perfect" drivers like the e1000e
all the time was a bad idea. We have a very repeatable testbed in
karlstad, already - I'm interested in what random sort of traffic can
exist on a home network that messes life up.

One of the things I noticed while using kodi is that the box announces
2k of multicast ipv4 packets every 30 seconds or so on the upnp
port... AND over 4k of multicast ipv6 packets, if ipv6 is enabled.

B) Need to be able to drive 802.11ac as hard as possible with as many
stations as possible.

C) needs to be low power and quiet (cheap is good too!)

Has anyone tried the banana pi? That's what comcast is using in their tests....

Re: [Cerowrt-devel] odroid C1+ status

[dpreed]

I have a Banana Pi, but I can't imagine why it would be useful as a router.
Why would Comcast even bother?  A Raspberry Pi 3 would be better, and far more available. (though I think the slow Ethernet port and low end WiFi on the Raspberry Pi 3 would make it sort of marginal, it's certainly quite fine for a low-end OpenWRT machine if you want to live at 50 Mb/sec)



On Saturday, March 5, 2016 3:23pm, "Dave Taht" <dave.taht@gmail.com> said:

> wow, thx for all the suggestions on alternate x86 router hardware... I
> will read more later.
> 
> Would using a blog format for things like the following work better
> for people? I could more easily revise, including graphics, etc,
> etc... could try to hit on our hot buttons (upgradability, bloat,
> reliability, kernel versions, manufacturer support) with some sort of
> grading system...
> 
> http://the-edge.taht.net/post/odroid_c1_plus/ in this case
> 
> ...
> 
> I got the odroid C1+ to work better. (either a cable or power supply
> issue, I swapped both). On output it peaks at about 416Mbits with 26%
> of cpu being spent in a softirq interrupt.  On input I can get it to
> gbit, with 220% of cpu in use.
> 
> The rrul tests were pretty normal, aside from the apparent 400mbit
> upload limit causing contention on rx/tx (at the moment I have no good
> place to put these test results since snapon is now behind a firewall.
> I'd like to get more organized about how we store and index these
> results also)
> 
> There is no BQL support in the odroid driver for it, and it ships with
> linux 3.10.80. At least its a LTS version.... I am totally unfamiliar
> with the odroid ecosystem but maybe there is active kernel dev on it
> somewhere?
> 
> (The pi 2, on the other hand, is kernel 4.1.17-v7 AND only has a
> 100mbit phy, so it is hard to complain about only getting 400mbit from
> the odroid c1+, but, dang it, a much later kernel would be nice in the
> odroid)
> 
> My goal in life, generally, is to have a set of boxes with known
> characteristics to drive tests with, that are reliable enough to setup
> once and ignore.
> 
> A) this time around, I definitely wanted variety, particularly in tcp
> implementations, kernel versions, ethernet and wifi chips - as it
> seemed like drawing conclusions from "perfect" drivers like the e1000e
> all the time was a bad idea. We have a very repeatable testbed in
> karlstad, already - I'm interested in what random sort of traffic can
> exist on a home network that messes life up.
> 
> One of the things I noticed while using kodi is that the box announces
> 2k of multicast ipv4 packets every 30 seconds or so on the upnp
> port... AND over 4k of multicast ipv6 packets, if ipv6 is enabled.
> 
> B) Need to be able to drive 802.11ac as hard as possible with as many
> stations as possible.
> 
> C) needs to be low power and quiet (cheap is good too!)
> 
> Has anyone tried the banana pi? That's what comcast is using in their tests....
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 

Re: [Cerowrt-devel] odroid C1+ status

[Dave Taht]

On Sat, Mar 5, 2016 at 2:19 PM,  <dpreed@reed.com> wrote:
> I have a Banana Pi, but I can't imagine why it would be useful as a router.

The banana pi is being used as the test generator in the comcast
bufferbloat test program.

> Why would Comcast even bother?  A Raspberry Pi 3 would be better, and far more available. (though I think the slow Ethernet port and low end WiFi on the Raspberry Pi 3 would make it sort of marginal, it's certainly quite fine for a low-end OpenWRT machine if you want to live at 50 Mb/sec)

What I had tried to do several times over the past years is have a
little monitoring box I could put out along the edges of the yurtlab
network, doing mrtg, smokeping, traceroute, and acting as a
netperf/iperf server. I'd ultimately settled on the beaglebone blacks
for this, but never got to where they would stay up long enough to be
useful.

Re: [Cerowrt-devel] odroid C1+ status

[Mikael Abrahamsson]

On Sat, 5 Mar 2016, dpreed@reed.com wrote:

> Why would Comcast even bother?  A Raspberry Pi 3 would be better, and 
> far more available. (though I think the slow Ethernet port and low end 
> WiFi on the Raspberry Pi 3 would make it sort of marginal, it's 
> certainly quite fine for a low-end OpenWRT machine if you want to live 
> at 50 Mb/sec)

I have a banana pi router, which has 1 WAN and 4 LAN. I haven't really 
used it that much, but during my initial testing it seemed that it at 
least had proper SOC connections to the ethernet ports, which gave it a 
lot better performance than the USB ethernet that the RPi has.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

Re: [Cerowrt-devel] odroid C1+ status

[David Lang]

A blog format for hardware testing would be a good idea.

David Lang

On Sat, 5 Mar 2016, Dave Taht wrote:

> Date: Sat, 5 Mar 2016 12:23:36 -0800
> From: Dave Taht <dave.taht@gmail.com>
> To: moeller0 <moeller0@gmx.de>
> Cc: "cerowrt-devel@lists.bufferbloat.net"
>     <cerowrt-devel@lists.bufferbloat.net>
> Subject: [Cerowrt-devel] odroid C1+ status
> 
> wow, thx for all the suggestions on alternate x86 router hardware... I
> will read more later.
>
> Would using a blog format for things like the following work better
> for people? I could more easily revise, including graphics, etc,
> etc... could try to hit on our hot buttons (upgradability, bloat,
> reliability, kernel versions, manufacturer support) with some sort of
> grading system...
>
> http://the-edge.taht.net/post/odroid_c1_plus/ in this case
>
> ...
>
> I got the odroid C1+ to work better. (either a cable or power supply
> issue, I swapped both). On output it peaks at about 416Mbits with 26%
> of cpu being spent in a softirq interrupt.  On input I can get it to
> gbit, with 220% of cpu in use.
>
> The rrul tests were pretty normal, aside from the apparent 400mbit
> upload limit causing contention on rx/tx (at the moment I have no good
> place to put these test results since snapon is now behind a firewall.
> I'd like to get more organized about how we store and index these
> results also)
>
> There is no BQL support in the odroid driver for it, and it ships with
> linux 3.10.80. At least its a LTS version.... I am totally unfamiliar
> with the odroid ecosystem but maybe there is active kernel dev on it
> somewhere?
>
> (The pi 2, on the other hand, is kernel 4.1.17-v7 AND only has a
> 100mbit phy, so it is hard to complain about only getting 400mbit from
> the odroid c1+, but, dang it, a much later kernel would be nice in the
> odroid)
>
> My goal in life, generally, is to have a set of boxes with known
> characteristics to drive tests with, that are reliable enough to setup
> once and ignore.
>
> A) this time around, I definitely wanted variety, particularly in tcp
> implementations, kernel versions, ethernet and wifi chips - as it
> seemed like drawing conclusions from "perfect" drivers like the e1000e
> all the time was a bad idea. We have a very repeatable testbed in
> karlstad, already - I'm interested in what random sort of traffic can
> exist on a home network that messes life up.
>
> One of the things I noticed while using kodi is that the box announces
> 2k of multicast ipv4 packets every 30 seconds or so on the upnp
> port... AND over 4k of multicast ipv6 packets, if ipv6 is enabled.
>
> B) Need to be able to drive 802.11ac as hard as possible with as many
> stations as possible.
>
> C) needs to be low power and quiet (cheap is good too!)
>
> Has anyone tried the banana pi? That's what comcast is using in their tests....
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

Re: [Cerowrt-devel] odroid C1+ status

[Luis E. Garcia]

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

+1
A blog format where we can also comment and document our experiences/tweaks.

On Saturday, March 5, 2016, David Lang <david@lang.hm> wrote:

> A blog format for hardware testing would be a good idea.
>
> David Lang
>
> On Sat, 5 Mar 2016, Dave Taht wrote:
>
> Date: Sat, 5 Mar 2016 12:23:36 -0800
>> From: Dave Taht <dave.taht@gmail.com>
>> To: moeller0 <moeller0@gmx.de>
>> Cc: "cerowrt-devel@lists.bufferbloat.net"
>>     <cerowrt-devel@lists.bufferbloat.net>
>> Subject: [Cerowrt-devel] odroid C1+ status
>>
>> wow, thx for all the suggestions on alternate x86 router hardware... I
>> will read more later.
>>
>> Would using a blog format for things like the following work better
>> for people? I could more easily revise, including graphics, etc,
>> etc... could try to hit on our hot buttons (upgradability, bloat,
>> reliability, kernel versions, manufacturer support) with some sort of
>> grading system...
>>
>> http://the-edge.taht.net/post/odroid_c1_plus/ in this case
>>
>> ...
>>
>> I got the odroid C1+ to work better. (either a cable or power supply
>> issue, I swapped both). On output it peaks at about 416Mbits with 26%
>> of cpu being spent in a softirq interrupt.  On input I can get it to
>> gbit, with 220% of cpu in use.
>>
>> The rrul tests were pretty normal, aside from the apparent 400mbit
>> upload limit causing contention on rx/tx (at the moment I have no good
>> place to put these test results since snapon is now behind a firewall.
>> I'd like to get more organized about how we store and index these
>> results also)
>>
>> There is no BQL support in the odroid driver for it, and it ships with
>> linux 3.10.80. At least its a LTS version.... I am totally unfamiliar
>> with the odroid ecosystem but maybe there is active kernel dev on it
>> somewhere?
>>
>> (The pi 2, on the other hand, is kernel 4.1.17-v7 AND only has a
>> 100mbit phy, so it is hard to complain about only getting 400mbit from
>> the odroid c1+, but, dang it, a much later kernel would be nice in the
>> odroid)
>>
>> My goal in life, generally, is to have a set of boxes with known
>> characteristics to drive tests with, that are reliable enough to setup
>> once and ignore.
>>
>> A) this time around, I definitely wanted variety, particularly in tcp
>> implementations, kernel versions, ethernet and wifi chips - as it
>> seemed like drawing conclusions from "perfect" drivers like the e1000e
>> all the time was a bad idea. We have a very repeatable testbed in
>> karlstad, already - I'm interested in what random sort of traffic can
>> exist on a home network that messes life up.
>>
>> One of the things I noticed while using kodi is that the box announces
>> 2k of multicast ipv4 packets every 30 seconds or so on the upnp
>> port... AND over 4k of multicast ipv6 packets, if ipv6 is enabled.
>>
>> B) Need to be able to drive 802.11ac as hard as possible with as many
>> stations as possible.
>>
>> C) needs to be low power and quiet (cheap is good too!)
>>
>> Has anyone tried the banana pi? That's what comcast is using in their
>> tests....
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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

Re: [Cerowrt-devel] odroid C1+ status

[John Yates]

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

On Sat, Mar 5, 2016 at 6:34 PM, Luis E. Garcia <luis@bitamins.net> wrote:

> +1
> A blog format where we can also comment and document our
> experiences/tweaks.
>

While blogs typically support threaded commenting they do little to support
curation of anything other than the main article. Perhaps a wiki would be
better.

/john

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

Re: [Cerowrt-devel] odroid C1+ status

[James Cloos]

>>>>> "DT" == Dave Taht <dave.taht@gmail.com> writes:

DT> There is no BQL support in the odroid driver for it, and it ships with
DT> linux 3.10.80. At least its a LTS version.... I am totally unfamiliar
DT> with the odroid ecosystem but maybe there is active kernel dev on it
DT> somewhere?

Linus pulled several c1 related patches in Feb, so there is a good
chance that his current kernel will work on the c1 and c1+.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6