Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Lockup at high speeds
Date: Sat, 02 Jun 2018 20:21:22 +0200	[thread overview]
Message-ID: <87a7sdcan1.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4rXiWO+QhRFtcmBETno_G+gF2Qq9CySrWE+n=0ERwcVw@mail.gmail.com>

Dave Taht <dave.taht@gmail.com> writes:

> How on earth are you getting these speeds? I'm stuck at a pathetic *4*
> gbit here on the admittedly ancient 12 core boxes I'd got.
> (I'll go rework my veth topology)

Well, having actual hardware do the packet forwarding, and only having
each machine process each packet once probably helps...

> rcu stuff makes me nervous, what happens if that nat stuff is disabled entirely.
>
> What if you made q.len and sparse/bullk flow counts atomic ops?

The whole qdisc dequeue op is running while holding a global lock. The
freezes I'm seeing are happening because the other cores get stuck
waiting for the cake dequeue operation to complete (and thus release the
qdisc lock). Which is why I suspect an infinite loop somewhere...

> I tend to lean towards an overflow post 40gbit also.

An overflow of what? 40 Gbps is 5 GBps, which is the unit that rates are
being measured in. So there's no obvious reason to expect that... Which
is not to say it couldn't happen, of course...

-Toke

  reply	other threads:[~2018-06-02 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 17:46 Toke Høiland-Jørgensen
2018-06-01 17:49 ` Jonathan Morton
2018-06-01 17:53   ` Toke Høiland-Jørgensen
2018-06-01 19:03     ` Georgios Amanakis
2018-06-01 19:23       ` Toke Høiland-Jørgensen
     [not found]         ` <9A273CA6-FDF6-485D-B466-8B01D4573BD9@gmail.com>
2018-06-01 19:58           ` Toke Høiland-Jørgensen
2018-06-02 17:08             ` Dave Taht
2018-06-02 18:21               ` Toke Høiland-Jørgensen [this message]
2018-06-02 18:55                 ` Dave Taht
2018-06-02 19:25                   ` Toke Høiland-Jørgensen
2018-06-03 14:56                     ` Georgios Amanakis
2018-06-03 23:26                       ` Toke Høiland-Jørgensen
2018-06-05 11:46                         ` Pete Heist
2018-06-05 14:24                           ` Pete Heist

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=87a7sdcan1.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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