Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Pedro Tumusok <pedro.tumusok@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] airfiber 60HD uses vpp + dpdk
Date: Mon, 14 Feb 2022 09:36:29 +0100	[thread overview]
Message-ID: <CACQiMXa_Zvy0NjxtYyaCtXqHz6=SXFpmuBtJaZg+LzOyunz=dg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7pa4hTb5hZ0kUqOtopKjNZ0bhHQT8x3EmZNF0_g+qY9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

Only thing i know that uses vpp + dpdk is TNSR.

https://www.netgate.com/tnsr

Not sure about som in that.

Pedro



On Sun, 13 Feb 2022, 16:18 Dave Taht, <dave.taht@gmail.com> wrote:

> discovered via:
>
> https://twitter.com/awlnx/status/1491785956944351232
>
> I last paid attention to these technologies, 5 years ago.
> https://lists.bufferbloat.net/pipermail/cake/2016-April/001884.html
>
> starlink's dishy also uses a userspace stack (not vpp or dpdk so far
> as I can tell). Not clear if either of these devices write the device
> itself directly (where's the ring buffer?) or use an overlying qdisc
> (seems unlikely).
>
> At least a few other devices are using vpp that I know of. vpp ripped
> out support for even RED a few years back. hqos is deprecated. What if
> anything replaced it?
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]

      reply	other threads:[~2022-02-14  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 15:18 [Cerowrt-devel] " Dave Taht
2022-02-14  8:36 ` Pedro Tumusok [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='CACQiMXa_Zvy0NjxtYyaCtXqHz6=SXFpmuBtJaZg+LzOyunz=dg@mail.gmail.com' \
    --to=pedro.tumusok@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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