From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [Cake] cake at 3gbit
Date: Thu, 31 May 2018 17:40:14 +0200 [thread overview]
Message-ID: <87fu27bzq9.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4cOmpSu=BCxEyY2_cW28YZmBQ-uVqyphwEwezOiAmXcA@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
> I DO have real 10GigE hardware now, but would love to see someone
> trying cake at 40GigE+ in the real world now that it allows
> superpackets and the api allows for more than 40Gbit to be specified.
I have had no problem saturating a 40Gig link with Cake on it with TCP
traffic. Even with the shaper enabled, I got pretty much to line rate,
IIRC (hence the change switching the rate parameter to 64 bits).
I just got some 100gig cards, so maybe there's a chance we can hit a
bottleneck with those. I'll do a quick test run shot once I get them
installed :)
-Toke
prev parent reply other threads:[~2018-05-31 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:32 Dave Taht
2018-05-31 15:40 ` Toke Høiland-Jørgensen [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/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=87fu27bzq9.fsf@toke.dk \
--to=toke@toke.dk \
--cc=brouer@redhat.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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