From: Dave Taht <dave.taht@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Libreqos at battlemesh?
Date: Fri, 10 May 2024 08:38:30 -0700 [thread overview]
Message-ID: <CAA93jw5zFotzmAAePWRJ9NBTXw=rmdq0uzWeEvBW545eoP5nUQ@mail.gmail.com> (raw)
In-Reply-To: <60336b6f-b5a9-44ba-874b-e997d47f43e6@arinc9.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
We don’t have hw in the eu. Basically a multi core x86 box with 4 or more
hardware network queues is needed. Does not need to be very high end but
the drivers need full bpf support.
Maybe the libreqos list has some low end suggestions
https://libreqos.readthedocs.io/en/latest/docs/SystemRequirements/Compute.html
On Thursday, May 9, 2024, Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
> If you have the hardware, bring it!
>
> Arınç
>
> On 10/05/2024 07:43, Dave Taht via Battlemesh wrote:
>
>> It would be so cool to slam a libreqos box inline with either your uplink
>> or the testbed and show yall all thr cool stats.
>>
>>
>>
>> _______________________________________________
>> Battlemesh mailing list
>> Battlemesh@ml.ninux.org
>> https://ml.ninux.org/mailman/listinfo/battlemesh
>>
>
--
https://www.youtube.com/watch?v=BVFWSyMp3xg&t=1098s Waves Podcast
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 1665 bytes --]
next parent reply other threads:[~2024-05-10 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw5bLQX9N474tQKUULmHnv36g61Bd0JR+E-3J3YT8Kby6Q@mail.gmail.com>
[not found] ` <60336b6f-b5a9-44ba-874b-e997d47f43e6@arinc9.com>
2024-05-10 15:38 ` Dave Taht [this message]
2024-05-10 17:26 ` Frantisek Borsik
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5zFotzmAAePWRJ9NBTXw=rmdq0uzWeEvBW545eoP5nUQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=battlemesh@ml.ninux.org \
--cc=libreqos@lists.bufferbloat.net \
/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