Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
	"Cake List" <cake@lists.bufferbloat.net>,
	"George Amanakis" <gamanakis@gmail.com>,
	"Pete Heist" <peteheist@gmail.com>,
	"Yuchung Cheng" <ycheng@google.com>,
	"Neal Cardwell" <ncardwell@google.com>,
	"Netfilter Development Mailinglist"
	<netfilter-devel@vger.kernel.org>
Subject: [Cake] issues with shaping cake to 60 gbits or in unlimited mode at 100gbps
Date: Mon, 4 Jun 2018 14:32:42 -0700	[thread overview]
Message-ID: <CAA93jw4KdC72309Y++-vanu4m_L6bwxY2k9EQSGbwJKgPYvEFg@mail.gmail.com> (raw)

I would like to point a finger at the mlx5 code rather than cake itself,
I am wondering if there is anyone out there with a different 100gps
capable device and setup that could give the sch_cake code a go?

we've been unable to duplicate the lockup we're seeing with the veth devices,
for example.

On Fri, Jun 1, 2018 at 11:17 AM, David Miller <davem@davemloft.net> wrote:
> From: Toke Høiland-Jørgensen <toke@toke.dk>
> Date: Fri, 01 Jun 2018 19:42:12 +0200
>
>> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>>
>>> This patch series adds the CAKE qdisc, and has been split up to ease
>>> review.
>>>
>>> I have attempted to split out each configurable feature into its own patch.
>>> The first commit adds the base shaper and packet scheduler, while
>>> subsequent commits add the optional features. The full userspace API and
>>> most data structures are included in this commit, but options not
>>> understood in the base version will be ignored.
>>
>> Hmm, there seems to be a lockup issue being triggered when running CAKE
>> at high speeds (>40 Gbps in my tests). Please drop this series for now,
>> we'll return for 4.19 with a revised version.
>
> Ok.
>
> Thanks for continuing to push this work along.



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

                 reply	other threads:[~2018-06-04 21:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4KdC72309Y++-vanu4m_L6bwxY2k9EQSGbwJKgPYvEFg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=davem@davemloft.net \
    --cc=gamanakis@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=peteheist@gmail.com \
    --cc=toke@toke.dk \
    --cc=ycheng@google.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