From: Herbert Wolverson <herberticus@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] if only we had budget...
Date: Fri, 4 Nov 2022 16:25:00 -0500 [thread overview]
Message-ID: <CA+erpM5=Ypm+B71jQp+Ukaq=a5d8CJxnW-bNqFTzgHyg4MOShg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6X5jrpZRnFJMpcePxh5NPvvp3EHLa+jiCQgXzM5=YRCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
If anyone feels like sending me one, I promise faithfully to make sure that
LibreQOS runs really well on it... ;-)
I honestly don't see any reason it wouldn't work. I'm not entirely sure
what the limit on NICs is for interrupt lines/interface queues that can be
converted into CPU bindings. It should scale pretty linearly until you run
out of mappable interface lines. (The same is true for the high-end ARM
servers)
On Fri, Nov 4, 2022 at 12:11 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> 64 cores, 800gbit, smart network cards...
>
> https://www.ieiworld.com/en/product/model.php?II=865
>
> Next year!! Or, what I expect is a lot 2+ year old 100Gbit data center
> gear to start getting sold off at various auction sales, which
> is more than we need and probably 1/10th the price.
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 1959 bytes --]
prev parent reply other threads:[~2022-11-04 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 17:11 Dave Taht
2022-11-04 21:25 ` Herbert Wolverson [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/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='CA+erpM5=Ypm+B71jQp+Ukaq=a5d8CJxnW-bNqFTzgHyg4MOShg@mail.gmail.com' \
--to=herberticus@gmail.com \
--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