Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Herbert Wolverson <herberticus@gmail.com>
To: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] DPDK vs XDP
Date: Thu, 13 Oct 2022 18:00:52 -0500	[thread overview]
Message-ID: <CA+erpM5K4v5AR+JT_TptRuA1qHE9kLiR+SHW-X27qdBvaCvVZA@mail.gmail.com> (raw)
In-Reply-To: <CAOZyJotPSp9cukhPq04ytUVw4yctxo-rFwJp7Z5zm9qUQuiZmA@mail.gmail.com>

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

Sorry I had to run - daycare schedule is tight if I want to park anywhere
remotely nearby.

I glanced through, and raising the hashmap/trie sizes is pretty
straightforward. The bigger problem looks to be the class numbering scheme
(major:minor). I wonder if it's possible to change the representation to
use 8 bits for Major/CPU and 24 for the minor? That would give us 16
million identifiers.

I'll try to research tomorrow.

On Thu, Oct 13, 2022, 5:48 PM Robert Chacón via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> If we can get the IP filtering limit upped from 32k and introduce virtual
> interfaces to split up HTBs as Toke suggested, we could see some crazy
> throughput thanks to XDP. Very exciting!
>
> On Thu, Oct 13, 2022 at 4:41 PM Dave Taht via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
>> I still get the giggles when I see the CPU usage on fig 4.
>>
>>
>> https://github.com/xdp-project/xdp-paper/blob/master/xdp-the-express-data-path.pdf
>>
>> DPDK is a great way to heat data centers.
>>
>> --
>> 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
>>
>
>
> --
> Robert Chacón
> CEO | JackRabbit Wireless LLC <http://jackrabbitwireless.com>
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>

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

      reply	other threads:[~2022-10-13 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 22:41 Dave Taht
2022-10-13 22:48 ` Robert Chacón
2022-10-13 23:00   ` 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+erpM5K4v5AR+JT_TptRuA1qHE9kLiR+SHW-X27qdBvaCvVZA@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