From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Matt Taggart" <matt@lackof.org>,
"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Minirouter with pi compute module 4
Date: Thu, 19 May 2022 15:06:50 -0400 (EDT) [thread overview]
Message-ID: <1652987210.624723955@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6qk9zXU3sdD2dDzK-Zj_1-8YnpZDwm=x_YjAPBQyAfQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]
Dave -
I'm certain that I have non-x86 devices that can forward more than a gbit/sec in both directions. If only because I have a very nice system based on LS2160A ARM implementation that I use to forward 10 GigE traffic in both directions. Though the packets are not tiny. It's not cheap, of course. I am running Fedora server on it in my lab. The LS2160A carrier comes from a company called SolidRun.
I do understand that many of the low end ARM boards (and maybe even the Pi4 Compute Module) have driver/bus weaknesses. Have you tried to understand what the issues are? Could be Linux kernel and driver issues specific to the GigE hardware. Though I'd assume that USB 3.1 would not inherently get in the way.
I currently use a Celeron board with 2 1 GigE interfaces for my 1Gig cable connection, running Linux configured according to my preferences. As you say, x86 boards and PCIe ethernet interfaces tend to be fine with two 1 GigE ports.
So maybe you want to be a bit more specific about what you mean "device on the market"?
On Thursday, May 19, 2022 2:46pm, "Dave Taht" <dave.taht@gmail.com> said:
> I am sadly re-discovering there is not a single device on the market
> outside the x86 universe that can actually forward a gbit in both
> directions at the same time.
>
>
> On Thu, May 19, 2022 at 1:36 PM Matt Taggart <matt@lackof.org> wrote:
> >
> > This looks like an interesting router candidate
> >
> >
> https://www.seeedstudio.com/Dual-GbE-Carrier-Board-with-4GB-RAM-32GB-eMMC-RPi-CM4-Case-p-5029.html
> >
> > Description says:
> > * one NIC is Broadcom BCM54210PE (from the CM4)
> > * the other is "Microchip's LAN7800" behind usb3
> > * 2 additional usb3 ports
> > * the usb3 uses the CM4's PCIe 2.0 x1 (500MB/s)
> > * wifi/BLE is the CM4's onboard, I think "Cypress CYW43455"?
> >
> > It sort of reminds me of the Espressobin device from a few years back,
> > but much faster and the pi has a much larger installed base, better
> > support, etc.
> >
> > --
> > Matt Taggart
> > matt@lackof.org
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 4108 bytes --]
prev parent reply other threads:[~2022-05-19 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 18:36 Matt Taggart
2022-05-19 18:46 ` Dave Taht
2022-05-19 19:06 ` David P. Reed [this message]
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=1652987210.624723955@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=matt@lackof.org \
/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