From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9F0123B2AF for ; Sat, 5 Mar 2016 15:23:36 -0500 (EST) Received: by mail-ob0-x232.google.com with SMTP id ts10so77409805obc.1 for ; Sat, 05 Mar 2016 12:23:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc; bh=AOpmNHa+G64eqQJrd0NQ3UfmAZCA6cMI4PV0Z7N41YA=; b=YB51vIjmdpFfyvw2i39+RZrZIsieppms5ZDuU8qVabiCY+mzS69oQnz7anyPG/91lL 8v54r2iSX/K1ksSnKREjDy6bYxzkB00NS7OJCXuFULyEoNcgy1DyrH8MoXUj9I/l/9mQ DrQ3OUPJhUoFbb7LTX09gGh9cPzhVBGDHpgxuEM9ZsGM2h1kmh91R4FoWCZPu3J85cpF 3lVSdaOUVkM8rqiILFFqr1AIn8dValmiYTnhGJMMSbW03Scw7EeoGftjxa2a8LS8ocvD jnUcc8g6jjWDw8BK1Vm79VA5VuY706KWmCvPsqWq3IE5jIikDzd9BXf9nKD8Xic73Igs vUUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc; bh=AOpmNHa+G64eqQJrd0NQ3UfmAZCA6cMI4PV0Z7N41YA=; b=gLXVkZiyVlh2vngkI0HigE9eiwZbeomf5LpNQMpY5jp/4Bj1V/JXTnBLDF/4jHhq4V 5I/HjY5cwNFvZvXRXJtXtfgDxpK3NzrRvV5PgxSO3hUSzKPcuORJdMtNXgDZZyTy+JDH Fktoc8P7xiewNtq0wLJe9/FEUPplg+gnJHBnDJGiLXPDaUKLsw3SbGQcjztRDWbOjO13 REHNDKWSvVtxjs8BJ9x7q6+Vxf/ZsypmqZ6gRfCL/LAoecrt8kBUK3su6417GoQx0VSX dYZwL11S3TRJUJoOFcbD0To29Qm9iLc29NrTPMTvYg98xbxHtqjNVPE+HGWXDyFS5Pi3 kzng== X-Gm-Message-State: AD7BkJI8qvX+kmHyjjx7TpOIhP/iohuIU4ZZvzogANCt435XBmKQ0BesydhP60TGOH9vZu/wpylH1fgWd1CjdQ== MIME-Version: 1.0 X-Received: by 10.60.70.1 with SMTP id i1mr10260044oeu.13.1457209416166; Sat, 05 Mar 2016 12:23:36 -0800 (PST) Received: by 10.202.79.12 with HTTP; Sat, 5 Mar 2016 12:23:36 -0800 (PST) Date: Sat, 5 Mar 2016 12:23:36 -0800 Message-ID: From: Dave Taht To: moeller0 Cc: Valent Turkovic , "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Subject: [Cerowrt-devel] odroid C1+ status X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2016 20:23:36 -0000 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....