Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: dave seddon <dave.seddon.ca@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Thu, 28 Sep 2023 14:44:53 +0300	[thread overview]
Message-ID: <6D098714-69DC-41D9-A7DC-E94FD9C77625@gmail.com> (raw)
In-Reply-To: <A1F18F7E-2A27-4F13-87B1-D55594FB69F7@gmail.com>

> On 19 Sep, 2023, at 1:07 am, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
>> Raspberry Pi 4's just aren't very good at networking because of their I/O architecture on the board, just as they are slow at USB in general. That's why the CM4 is interesting. It's interesting that the PiHole has gotten so popular - it would run better on an Pi with a better network architecture.
> 
> On the contrary, the Pi 4 has an excellent I/O architecture compared to most of its peers, and especially compared to the previous Pis.  The built-in NIC is internal to the SoC and *NOT* attached via USB any more, so it can genuinely support gigabit speeds.  The USB interface is also fast enough to support a second GigE NIC, though the latency wouldn't be as good as one attached over PCIe.  That's with a standard, off-the-shelf Pi 4B.

Timely breaking news:  the Raspberry Pi 5 has just been announced.

The important new feature here (for us) is that it exposes a PCIe bus lane on the standard model, so you don't have to mess around with the Compute Module just to get access to that.  The built-in Ethernet port is now implemented in a PCIe-attached "southbridge" chip, and the WiFi performance has been improved by accelerating the interface by which the radio is attached.

On the downside, the price has gone up.

 - Jonathan Morton

  reply	other threads:[~2023-09-28 11:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  1:05 Dave Taht
2023-09-18  1:25 ` Jonathan Morton
2023-09-18 16:57 ` David P. Reed
2023-09-18 19:50 ` dave seddon
2023-09-18 20:24   ` David P. Reed
2023-09-18 22:07     ` Jonathan Morton
2023-09-28 11:44       ` Jonathan Morton [this message]
2023-09-28 12:15         ` Sebastian Moeller
2023-09-28 12:33           ` Jonathan Morton
2023-09-28 12:56             ` David Lang
2023-09-28 13:08             ` Sebastian Moeller
2023-09-28 13:19               ` David Lang
2023-09-28 13:27                 ` Sebastian Moeller
2023-10-13 15:59                   ` dave seddon
2023-10-13 17:25                     ` dave seddon
2023-10-15 15:11                       ` dave seddon
2023-10-15 15:52                         ` Sebastian Moeller
2023-10-15 16:24                           ` dave seddon
2023-10-15 20:29                             ` David P. Reed
2023-10-16  3:52                               ` Jonathan Morton
2023-10-15 15:53                         ` Dave Taht
2023-10-23 20:31                         ` dave seddon
2023-10-23 20:35                           ` dave seddon
2023-10-24 16:27                           ` dave seddon
2023-10-24 21:35                             ` dave seddon
2023-10-24 22:06                               ` Dave Taht
2023-09-18 22:13   ` Jonathan Morton
2023-09-18 22:52     ` dave seddon
2023-09-18 23:08       ` Jonathan Morton

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6D098714-69DC-41D9-A7DC-E94FD9C77625@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.seddon.ca@gmail.com \
    --cc=dpreed@deepplum.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