From: David Miller <davem@davemloft.net>
To: toke@redhat.com
Cc: netdev@vger.kernel.org, cake@lists.bufferbloat.net
Subject: Re: [Cake] [PATCH net] sch_cake: Take advantage of skb->hash where appropriate
Date: Sat, 30 May 2020 21:52:43 -0700 (PDT) [thread overview]
Message-ID: <20200530.215243.413220351888088239.davem@davemloft.net> (raw)
In-Reply-To: <20200529124344.355785-1-toke@redhat.com>
From: Toke Høiland-Jørgensen <toke@redhat.com>
Date: Fri, 29 May 2020 14:43:44 +0200
> While the other fq-based qdiscs take advantage of skb->hash and doesn't
> recompute it if it is already set, sch_cake does not.
>
> This was a deliberate choice because sch_cake hashes various parts of the
> packet header to support its advanced flow isolation modes. However,
> foregoing the use of skb->hash entirely loses a few important benefits:
>
> - When skb->hash is set by hardware, a few CPU cycles can be saved by not
> hashing again in software.
>
> - Tunnel encapsulations will generally preserve the value of skb->hash from
> before the encapsulation, which allows flow-based qdiscs to distinguish
> between flows even though the outer packet header no longer has flow
> information.
>
> It turns out that we can preserve these desirable properties in many cases,
> while still supporting the advanced flow isolation properties of sch_cake.
> This patch does so by reusing the skb->hash value as the flow_hash part of
> the hashing procedure in cake_hash() only in the following conditions:
>
> - If the skb->hash is marked as covering the flow headers (skb->l4_hash is
> set)
>
> AND
>
> - NAT header rewriting is either disabled, or did not change any values
> used for hashing. The latter is important to match local-origin packets
> such as those of a tunnel endpoint.
>
> The immediate motivation for fixing this was the recent patch to WireGuard
> to preserve the skb->hash on encapsulation. As such, this is also what I
> tested against; with this patch, added latency under load for competing
> flows drops from ~8 ms to sub-1ms on an RRUL test over a WireGuard tunnel
> going through a virtual link shaped to 1Gbps using sch_cake. This matches
> the results we saw with a similar setup using sch_fq_codel when testing the
> WireGuard patch.
>
> Fixes: 046f6fd5daef ("sched: Add Common Applications Kept Enhanced (cake) qdisc")
> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Applied to net-next, thanks.
prev parent reply other threads:[~2020-05-31 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 12:43 Toke Høiland-Jørgensen
2020-05-29 13:02 ` Toke Høiland-Jørgensen
2020-05-29 17:57 ` Jakub Kicinski
2020-05-29 18:31 ` Toke Høiland-Jørgensen
2020-05-31 4:52 ` David Miller [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=20200530.215243.413220351888088239.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cake@lists.bufferbloat.net \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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