From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Sebastian Moeller <moeller0@gmx.de>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Marvell 385
Date: Sat, 25 Aug 2018 21:29:29 -0700 [thread overview]
Message-ID: <CAA93jw4wxp1AbvmbqnmSOLCxnTc5G2_RSop7cv4qkecbj_T3Eg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1808231719250.23215@uplift.swm.pp.se>
On Thu, Aug 23, 2018 at 8:32 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Thu, 23 Aug 2018, Sebastian Moeller wrote:
>
> > router should be able to handle at least the sold plan's bandwidth with
> > its main CPU...)
>
> There is exactly one SoC on the market that does this, and that's Marvell
> Armada 385, and it hasn't been very successful when it comes to ending up
> in these kinds of devices. It's mostly ended up in NASes and devices such
> as WRT1200AC, WRT1900ACS, WRT3200AC.
I just pulled two of those out of my junk drawer. (bricked presently).
It looks like we
can't apply fq_codel for wifi to it (big binary blob), still.
The firmware interface code is pretty clean though.
https://github.com/kaloz/mwlwifi
I rather liked the 385 chip myself, but wifi... can't fix, going back
in junk drawer
unless someone wants one.
The expressobin is a Marvell Armada "3700LP (88F3720) dual core ARM
Cortex A53 processor up to 1.2GHz" - how does that compare? I have
plenty of ath10k and ath9k pcmcia cards....
>
> > Sure doing less/ a half asses job is less costly than doing it
> > right, but in the extreme not doing the job at all saves even more
> > energy ;). And I am not sure we are barking up the right tree here, it
> > is not that all home CPE are rigorously optimized for low power and
> > energy saving... my gut feeling is that the only optimizing principle is
> > cost for the manufacturer/OEM and that causes underpowered CPU that are
> > packet-accerlerated"-doped to appear to be able to do their job. I might
> > be wrong though, as I have ISP internal numbers on this issue.
>
> The CPU power and RAM/flash has crept up a lot in the past 5 years because
> other requirements in having the HGW support other applications than just
> being a very simple NAT44+wifi router.
>
> Cost is definitely an optimization, and when you're expected to have a
> price-to-customer including software in the 20-40 EUR/device range, then
> the SoC can't cost much. There has also been a lot of vendor lock-in.
>
> But now speeds are creeping up even more, we're now seeing 2.5GE and 10GE
> platforms, which require substantial CPU power to do forwarding. The Linux
> kernel is now becoming the bottleneck in the forwarding, not even on a
> 3GHz Intel CPU is it possible to forward even 10GE using the normal Linux
> kernel path (my guess right now is that this is due to context switching
> etc, not really CPU performance).
>
> Marvell has been the only one to really aim for lots of CPU performance in
> their SoC, there might be others now going the same path but it's also a
> downside if the CPU becomes bogged down with packet forwarding when it's
> also expected to perform other tasks on behalf of the user (and ISP).
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-08-26 4:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 0:49 [Bloat] beating the drum for BQL Dave Taht
2018-08-23 5:47 ` Mikael Abrahamsson
2018-08-23 13:06 ` [Bloat] [Cerowrt-devel] " Sebastian Moeller
2018-08-23 13:57 ` Jan Ceuleers
2018-08-23 14:22 ` Sebastian Moeller
2018-08-23 15:32 ` Mikael Abrahamsson
2018-08-23 17:14 ` Rosen Penev
2018-08-23 17:50 ` Mikael Abrahamsson
2018-08-23 18:21 ` Dave Taht
2018-08-23 20:15 ` Dave Taht
2018-08-24 7:00 ` Mikael Abrahamsson
2018-08-24 8:06 ` Dave Taht
2018-08-24 11:22 ` Toke Høiland-Jørgensen
2018-08-24 11:46 ` Jan Ceuleers
2018-08-24 13:43 ` Jan Ceuleers
2018-08-24 13:44 ` Mikael Abrahamsson
2018-08-24 13:56 ` Jan Ceuleers
2018-08-24 13:36 ` Mikael Abrahamsson
2018-08-24 7:05 ` Mikael Abrahamsson
2018-08-24 11:24 ` Toke Høiland-Jørgensen
2018-08-23 21:01 ` Toke Høiland-Jørgensen
2018-08-24 14:44 ` Dave Taht
2018-08-24 17:58 ` Toke Høiland-Jørgensen
2018-08-23 23:35 ` Sebastian Moeller
2018-08-24 1:08 ` David Collier-Brown
2018-08-24 6:16 ` Jan Ceuleers
2018-08-24 11:27 ` Toke Høiland-Jørgensen
2018-08-24 12:46 ` Pedro Tumusok
2018-08-24 13:09 ` Michael Richardson
2018-08-24 13:37 ` Mikael Abrahamsson
2018-08-24 13:44 ` Toke Høiland-Jørgensen
2018-08-26 4:29 ` Dave Taht [this message]
2018-08-26 4:32 ` [Bloat] Marvell 385 Jonathan Morton
2018-08-26 16:28 ` Rosen Penev
2018-08-26 18:44 ` Mikael Abrahamsson
2018-08-26 20:53 ` Dave Taht
2018-08-26 20:58 ` Rosen Penev
2018-08-26 21:08 ` Dave Taht
2018-08-27 0:55 ` Rosen Penev
2018-08-27 1:21 ` Dave Taht
2018-08-27 1:33 ` Rosen Penev
2018-08-27 1:45 ` Dave Taht
2018-08-27 1:53 ` Rosen Penev
2018-08-27 11:33 ` Mikael Abrahamsson
2018-08-23 8:26 ` [Bloat] beating the drum for BQL Pete Heist
2018-08-23 10:51 ` Mikael Abrahamsson
2018-08-23 11:38 ` Pete Heist
2018-08-24 17:13 ` Pete Heist
2018-08-24 17:30 ` Dave Taht
2018-08-24 18:43 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4wxp1AbvmbqnmSOLCxnTc5G2_RSop7cv4qkecbj_T3Eg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=swmike@swm.pp.se \
/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