From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] another contender for WNDR replacement
Date: Tue, 20 Jan 2015 00:44:53 +0100 [thread overview]
Message-ID: <B9AD3704-2E24-41A0-B4F2-85E07A5B00FB@gmx.de> (raw)
In-Reply-To: <CAA93jw40fBwdgYb-Ff_W66v1tYAeSk+QO0B4zsZV=az0n7sfkg@mail.gmail.com>
Hi Dave, hi list,
On Jan 19, 2015, at 17:37 , Dave Taht <dave.taht@gmail.com> wrote:
> oh, they are using a nice ethernet chip from intel? That will help.
>
> I did feel the apu1c was improvable,
well, for what it is worth the apu1c is EOL’d and replaced by the apu1d, no idea what the difference is, both use an AMD low power/performance from last generation ;)
> but the intel "dma to cache"
> since ivy bridge feature is a tremendous advantage for intel chips.
But the fitlet uses a slightly more modern AMD design (I think its jaguar/puma instead of bobcat, whatever that means, technologically I mean, I am on top of the biologic difference between the two ;) ) I would not bet money that this can saturate its gigabit ethernet ports, but I think the immediate goal is a reasonably low priced device that allows SQM on current bandwidths <= 300Mbps combined. Maybe this is it...
>
> Sigh, more benchmarking….
More waiting ;) I think the dual and quad ethernet devices are not out yet …
Best Regards
Sebastian
>
> On Mon, Jan 19, 2015 at 5:46 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> Hi List,
>> the following might just be what we need to replace the WNDR as a hig(er)-speed capable traffic shaper:
>>
>> http://www.fit-pc.com/web/products/specifications/fitlet-models-specifications/?model%5B%5D=fitlet-B+%28TBA%29&model%5B%5D=fitlet-X+%28TBA%29&model%5B%5D=fitlet-i+%28TBA%29
>>
>> The entry level model fitlet-B is estimated at $129 (requires ram and msata), no information about the more interesting fitlet-i (2 GE ports). The AMD Jaguar SoC is supposedly more powerfull then the AMD G series T40E in the pc-engines api-1d ( http://www.pcengines.ch/apu1d.htm ) that was not that hot network wise ( http://planet.ipfire.org/post/pc-engines-apu1c-a-review ). Improvements include twice the L2, slightly faster DRAM, slightly tweaked core, an potentially “turbo” up to 1.6Ghz from 1GHz base, intel GE chip i211 with BQL support. Downside the intel AC wifi card most likely will not allow proper tweaking (so maybe not suited for the make-wifi-fast project)
>> So most likely this thing will also not be able to do SQM/Cake at 300Mbps combined or better. Would it not be sweet to finally be able to “retire” the wndrs…
>>
>> Best Regards
>> Sebastian
>>
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next prev parent reply other threads:[~2015-01-19 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:46 Sebastian Moeller
2015-01-19 16:37 ` Dave Taht
2015-01-19 23:44 ` Sebastian Moeller [this message]
2015-01-25 11:09 ` Felix Fietkau
2015-01-25 19:16 ` Dave Taht
2015-01-25 19:28 ` Felix Fietkau
2015-02-18 9:28 ` Sebastian Moeller
2015-02-18 9:30 ` Dave Taht
2015-02-18 9:38 ` Dave Taht
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=B9AD3704-2E24-41A0-B4F2-85E07A5B00FB@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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