From: "Adam Moffett" <adam@plexicomm.net>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake implementations
Date: Fri, 22 Nov 2019 13:33:36 +0000 [thread overview]
Message-ID: <em281f0a9b-a12d-4f64-8eab-6e13f4c7804f@adam-pc> (raw)
In-Reply-To: <878so85e2d.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
>
>> Second concern is that many of our equipment vendors already use
>> Linux. Even Cisco now in some products. Maybe we'll waste our time
>> trying to roll our own solution and then find that a software update
>> from a vendor next year gives us everything we needed anyway.
>
>This would be great, of course, and do go and bug your vendors to solve
>this problem! Note, however, that just because a system is running
>Linux on the control plane, it may be using a hardware-offloaded data
>plane that does not have any of the bufferbloat mitigation features
>(unless the vendor specifically implemented them). I'm hoping that
>*eventually* these things will be ubiquitous across the industry, but
>thus far this has seemed to be an "any decade now" kind of proposition :/
>
>-Toke
That's a great point.
Is the software more or less CPU independent? Would we run into any
known problems with a 72-core Tilera platform?
Thanks for all your help and input by the way.
-Adam
[-- Attachment #2: Type: text/html, Size: 2481 bytes --]
next prev parent reply other threads:[~2019-11-22 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 21:05 Adam Moffett
2019-11-21 21:53 ` Dave Taht
2019-11-22 11:07 ` Adam Moffett
2019-11-22 11:46 ` Toke Høiland-Jørgensen
2019-11-22 12:09 ` Justin Kilpatrick
2019-11-22 12:59 ` Toke Høiland-Jørgensen
2019-11-22 13:33 ` Adam Moffett [this message]
2019-11-22 14:26 ` Jonathan Morton
2019-11-22 14:33 ` Toke Høiland-Jørgensen
2019-11-22 16:40 ` Jesper Dangaard Brouer
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em281f0a9b-a12d-4f64-8eab-6e13f4c7804f@adam-pc \
--to=adam@plexicomm.net \
--cc=cake@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