Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Outback Dingo <outbackdingo@gmail.com>
To: dpreed@deepplum.com
Cc: toke@toke.dk, cake@lists.bufferbloat.net,
	 cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cake] [Cerowrt-devel] expressobin
Date: Wed, 1 Aug 2018 14:56:47 +0200	[thread overview]
Message-ID: <CAKYr3zz3yMjwjdAmFz203Gv7zQ4QmR7Bg8SRiKWdCmK8E5iy_w@mail.gmail.com> (raw)
In-Reply-To: <1533127753.40561414@apps.rackspace.com>

as a side note, has anyone done any sqm/cake work on say yocto or legato ??
On Wed, Aug 1, 2018 at 2:49 PM dpreed@deepplum.com <dpreed@deepplum.com> wrote:
>
> Yeah. Small FF 2 port Celeron board is what I use. And I have a 4 port Atom that runs like a bat out of hell.
>
> Currenty fiddling with Xilinx Dev boards, just put packet processing in FPGA for Cake, and no problem with 2.5 - 10 Gb/sec. Just need a free piece of low level SFP+ interfacing logic.
>
> My use case is using the open ChipLink/TileLink bus from RISCV rather than PCIe, making something that might be an open source ASIC design.
>
>
> -----Original Message-----
> From: "Toke Høiland-Jørgensen" <toke@toke.dk>
> Sent: Wed, Aug 1, 2018 at 5:23 am
> To: "Dave Taht" <dave.taht@gmail.com>, "Daniel Ezell" <dezell@stonescry.com>
> Cc: "Dave Taht" <dave.taht@gmail.com>, "Daniel Ezell" <dezell@stonescry.com>, "Cake List" <cake@lists.bufferbloat.net>, cerowrt-devel@lists.bufferbloat.net
> Subject: Re: [Cerowrt-devel] expressobin
>
> Dave Taht  writes:
>
> > It turns out it's just two ethernets with one, connected to a 2 port
> > switch. Not what I wanted. I'd wanted something different from the
> > apu2 or edgerouter X to play with, and I know the mvneta driver was
> > bql'd.
>
> I bought one of these to play with:
> https://teklager.se/en/products/routers/tlsense-i3-4lan
>
> x86 (i3 processor), four real ethernet ports, and passively cooled. A
> bit pricy, though; more than $400... But doubles well as a combined
> switch and media player :)
>
> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

  reply	other threads:[~2018-08-01 12:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 12:49 dpreed
2018-08-01 12:56 ` Outback Dingo [this message]
2018-08-01 20:06 ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2018-08-03 15:30 dpreed
2018-08-03 16:23 ` Michel Blais
2018-08-03 16:43   ` Jonathan Morton
2018-08-03 17:50     ` Michel Blais
2018-08-03 18:21       ` Jonathan Morton
2018-08-03 22:55 ` Joel Wirāmu Pauling
2018-08-01 12:40 dpreed
2018-08-01  2:54 [Cake] expressobin Dave Taht
     [not found] ` <CANp2as9-Kh_xr27Eth3Gtn=G0OC7o7riFoL2ZQn9rM2Fdd+o5g@mail.gmail.com>
2018-08-01  3:10   ` [Cake] [Cerowrt-devel] expressobin Dave Taht
2018-08-01  9:23     ` Toke Høiland-Jørgensen
2018-08-01 13:35 ` Mikael Abrahamsson

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=CAKYr3zz3yMjwjdAmFz203Gv7zQ4QmR7Bg8SRiKWdCmK8E5iy_w@mail.gmail.com \
    --to=outbackdingo@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=toke@toke.dk \
    /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