Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Aaron Wood" <woody77@gmail.com>,
	"Cake List" <cake@lists.bufferbloat.net>,
	"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>,
	"bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat]  New board that looks interesting
Date: Sun, 5 Apr 2020 16:17:40 -0400 (EDT)	[thread overview]
Message-ID: <1586117860.861216157@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4wDVyh9ZwXMuDt0=c0JTKVKkMG9WGnR5wJ1TYUh+LTjw@mail.gmail.com>

FYI - Fedora 31 continued not trying to "make my life easier" by inventing new packaging and containerization in the base distro. I think the folks who make Ubuntu think it is a consumer product.  Making it harder to self-configure in developer-hacker friendly ways.

I expect Fedora32 will have Wireguard (if not earlier).

On Saturday, April 4, 2020 1:36pm, "Dave Taht" <dave.taht@gmail.com> said:

> I think I'll wait for y'all to try it and report back. I trust my
> apu2s and I actually kind of like they lack a graphics chip and need
> to be configured via serial port.
> 
> In other news I've started testing ubuntu 20.4, which among other
> things, has wireguard in it. I've been really frustrated with the
> state of distributions lately, trying to get any complex thing done
> has required snaps and docker containers and I really prefer running
> stuff natively when possible. Tools that I still rely on like mrtg and
> smokeping are undermaintained, trying to get zoneminder to co-exist
> and co-install with anything else (notably jitsi thus far) has been a
> real PITA.
> 
> I am pleased at the increasing size of the ipv6 deployment, my phone
> got it last month....
> 
> I think I've found a babel bug with default routes...
> 
> and I fired up a kernel build to go hack on the ax200 chips.
> 
> On Sat, Apr 4, 2020 at 9:27 AM Aaron Wood <woody77@gmail.com> wrote:
>>
>> The comparison of chipset performance link (to OpemWRT forums) that went out had
>> this chip, the J4105 as the fastest.  Able to do a gigabit with cake (nearly able
>> to do it in both directions).
>>
>> I think this has replaced the apu2 as the board I’m going with as my edge
>> router.
>>
>> On Sat, Apr 4, 2020 at 9:10 AM Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> Historically I've found the "Celeron" chips rather weak, but it's just
>>> a brand. I haven't the foggiest idea how well this variant will
>>> perform.
>>>
>>> The intel ethernet chips are best of breed in linux, however. It's
>>> been my hope that the 211 variant with the timed networking support
>>> would show up in the field (sch_etx) so we could fiddle with that,
>>> (the apu2s aren't using that version) but I cannot for the life of me
>>> remember the right keywords to look it up at the moment. this feature
>>> lets you program when a packet emerges from the driver and is sort of
>>> a whole new ballgame when it comes to scheduling - there hasn't been
>>> an aqm designed for it, and you can do fq by playing tricks with the
>>> sent timestamp.
>>>
>>> All the other features look rather nice on this board.
>>>
>>> On Sat, Apr 4, 2020 at 7:47 AM David P. Reed <dpreed@deepplum.com> wrote:
>>> >
>>> > Thanks! I ordered one just now. In my experience, this company does rather
>>> neat stuff. Their XMOS based microphone array (ReSpeaker) is really useful.
>>> What's the state of play in Linux/OpenWRT for Intel 9560 capabilities
>>> regarding AQM?
>>> >
>>> > On Saturday, April 4, 2020 12:12am, "Aaron Wood" <woody77@gmail.com> said:
>>> >
>>> > > _______________________________________________
>>> > > Cake mailing list
>>> > > Cake@lists.bufferbloat.net
>>> > > https://lists.bufferbloat.net/listinfo/cake
>>> > > https://www.seeedstudio.com/ODYSSEY-X86J4105800-p-4445.html
>>> > >
>>> > > quad-core Celeron J4105 1.5-2.5 GHz x64
>>> > > 8GB Ram
>>> > > 2x i211t intel ethernet controllers
>>> > > intel 9560 802.11ac (wave2) wifi/bluetooth chipset
>>> > > intel built-in graphics
>>> > > onboard ARM Cortex-M0 and RPi & Arduino headers
>>> > > m.2 and PCIe adapters
>>> > > <$200
>>> > >
>>> >
>>> >
>>> > _______________________________________________
>>> > Bloat mailing list
>>> > Bloat@lists.bufferbloat.net
>>> > https://lists.bufferbloat.net/listinfo/bloat
>>>
>>>
>>>
>>> --
>>> Make Music, Not War
>>>
>>> Dave Täht
>>> CTO, TekLibre, LLC
>>> http://www.teklibre.com
>>> Tel: 1-831-435-0729
>>
>> --
>> - Sent from my iPhone.
> 
> 
> 
> --
> Make Music, Not War
> 
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
> 



  reply	other threads:[~2020-04-05 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04  4:12 [Cake] " Aaron Wood
2020-04-04 14:47 ` David P. Reed
2020-04-04 16:10   ` [Cake] [Bloat] " Dave Taht
2020-04-04 16:27     ` Aaron Wood
2020-04-04 17:36       ` Dave Taht
2020-04-05 20:17         ` David P. Reed [this message]
2020-04-27  2:45       ` Dave Taht
2020-12-18 23:48         ` Aaron Wood
2021-01-04  2:11           ` Dean Scarff

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=1586117860.861216157@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=woody77@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