Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: "Aaron A. Glenn" <aag@predictedpaths.nl>
To: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] 100gbit open source smart nic
Date: Thu, 03 Nov 2022 09:12:29 +0100	[thread overview]
Message-ID: <44b8991b-5ec1-4b6c-ba1f-9d6de2a72114@app.fastmail.com> (raw)
In-Reply-To: <CAA93jw7+R_=HE1ZbX5ncbyZggGa229mfwD0cuUgpgZCQCcJ3pg@mail.gmail.com>



On Thu, Nov 3, 2022, at 09:05, Dave Taht wrote:
>
> I'd settle for enough TCAM to interrupt the right processor to do the
> shaping, fq and aqm.

I hesitate to be ignorant in public but I don’t follow (how is TCAM used in this scenario? and what’s the correct processor?)

> What kind of pricing?

I don’t get anything better than what colfax direct and terasic.com.tw publicly post.

>> --
>>   Aaron A. Glenn
>> Predicted Paths BV

      reply	other threads:[~2022-11-03  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  7:52 Dave Taht
2022-11-03  7:56 ` Aaron A. Glenn
2022-11-03  8:05   ` Dave Taht
2022-11-03  8:12     ` Aaron A. Glenn [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=44b8991b-5ec1-4b6c-ba1f-9d6de2a72114@app.fastmail.com \
    --to=aag@predictedpaths.nl \
    --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