Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [PATCH net-next v12 4/7] sch_cake: Add NAT awareness to packet classifier
Date: Wed, 16 May 2018 23:14:44 +0200	[thread overview]
Message-ID: <87o9hfuwu3.fsf@toke.dk> (raw)
In-Reply-To: <CAM_iQpUCB24x7d7oDYkes_ngQ==8CjiwGqCBit-BK5NxzzZODg@mail.gmail.com>

Cong Wang <xiyou.wangcong@gmail.com> writes:

> On Wed, May 16, 2018 at 1:29 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> When CAKE is deployed on a gateway that also performs NAT (which is a
>> common deployment mode), the host fairness mechanism cannot distinguish
>> internal hosts from each other, and so fails to work correctly.
>>
>> To fix this, we add an optional NAT awareness mode, which will query the
>> kernel conntrack mechanism to obtain the pre-NAT addresses for each packet
>> and use that in the flow and host hashing.
>>
>> When the shaper is enabled and the host is already performing NAT, the cost
>> of this lookup is negligible. However, in unlimited mode with no NAT being
>> performed, there is a significant CPU cost at higher bandwidths. For this
>> reason, the feature is turned off by default.
>>
>> Signed-off-by: Toke Høiland-Jørgensen <toke@toke.dk>
>> ---
>>  net/sched/sch_cake.c |   73 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 73 insertions(+)
>>
>> diff --git a/net/sched/sch_cake.c b/net/sched/sch_cake.c
>> index 65439b643c92..e1038a7b6686 100644
>> --- a/net/sched/sch_cake.c
>> +++ b/net/sched/sch_cake.c
>> @@ -71,6 +71,12 @@
>>  #include <net/tcp.h>
>>  #include <net/flow_dissector.h>
>>
>> +#if IS_REACHABLE(CONFIG_NF_CONNTRACK)
>> +#include <net/netfilter/nf_conntrack_core.h>
>> +#include <net/netfilter/nf_conntrack_zones.h>
>> +#include <net/netfilter/nf_conntrack.h>
>> +#endif
>> +
>>  #define CAKE_SET_WAYS (8)
>>  #define CAKE_MAX_TINS (8)
>>  #define CAKE_QUEUES (1024)
>> @@ -514,6 +520,60 @@ static bool cobalt_should_drop(struct cobalt_vars *vars,
>>         return drop;
>>  }
>>
>> +#if IS_REACHABLE(CONFIG_NF_CONNTRACK)
>> +
>> +static void cake_update_flowkeys(struct flow_keys *keys,
>> +                                const struct sk_buff *skb)
>> +{
>> +       const struct nf_conntrack_tuple *tuple;
>> +       enum ip_conntrack_info ctinfo;
>> +       struct nf_conn *ct;
>> +       bool rev = false;
>> +
>> +       if (tc_skb_protocol(skb) != htons(ETH_P_IP))
>> +               return;
>> +
>> +       ct = nf_ct_get(skb, &ctinfo);
>> +       if (ct) {
>> +               tuple = nf_ct_tuple(ct, CTINFO2DIR(ctinfo));
>> +       } else {
>> +               const struct nf_conntrack_tuple_hash *hash;
>> +               struct nf_conntrack_tuple srctuple;
>> +
>> +               if (!nf_ct_get_tuplepr(skb, skb_network_offset(skb),
>> +                                      NFPROTO_IPV4, dev_net(skb->dev),
>> +                                      &srctuple))
>> +                       return;
>> +
>> +               hash = nf_conntrack_find_get(dev_net(skb->dev),
>> +                                            &nf_ct_zone_dflt,
>> +                                            &srctuple);
>> +               if (!hash)
>> +                       return;
>> +
>> +               rev = true;
>> +               ct = nf_ct_tuplehash_to_ctrack(hash);
>> +               tuple = nf_ct_tuple(ct, !hash->tuple.dst.dir);
>> +       }
>> +
>> +       keys->addrs.v4addrs.src = rev ? tuple->dst.u3.ip : tuple->src.u3.ip;
>> +       keys->addrs.v4addrs.dst = rev ? tuple->src.u3.ip : tuple->dst.u3.ip;
>> +
>> +       if (keys->ports.ports) {
>> +               keys->ports.src = rev ? tuple->dst.u.all : tuple->src.u.all;
>> +               keys->ports.dst = rev ? tuple->src.u.all : tuple->dst.u.all;
>> +       }
>> +       if (rev)
>> +               nf_ct_put(ct);
>> +}
>> +#else
>> +static void cake_update_flowkeys(struct flow_keys *keys,
>> +                                const struct sk_buff *skb)
>> +{
>> +       /* There is nothing we can do here without CONNTRACK */
>> +}
>> +#endif
>> +
>>  /* Cake has several subtle multiple bit settings. In these cases you
>>   *  would be matching triple isolate mode as well.
>>   */
>> @@ -541,6 +601,9 @@ static u32 cake_hash(struct cake_tin_data *q, const struct sk_buff *skb,
>>         skb_flow_dissect_flow_keys(skb, &keys,
>>                                    FLOW_DISSECTOR_F_STOP_AT_FLOW_LABEL);
>>
>> +       if (flow_mode & CAKE_FLOW_NAT_FLAG)
>> +               cake_update_flowkeys(&keys, skb);
>> +
>>         /* flow_hash_from_keys() sorts the addresses by value, so we have
>>          * to preserve their order in a separate data structure to treat
>>          * src and dst host addresses as independently selectable.
>> @@ -1727,6 +1790,12 @@ static int cake_change(struct Qdisc *sch, struct nlattr *opt,
>>                 q->flow_mode = (nla_get_u32(tb[TCA_CAKE_FLOW_MODE]) &
>>                                 CAKE_FLOW_MASK);
>>
>> +       if (tb[TCA_CAKE_NAT]) {
>> +               q->flow_mode &= ~CAKE_FLOW_NAT_FLAG;
>> +               q->flow_mode |= CAKE_FLOW_NAT_FLAG *
>> +                       !!nla_get_u32(tb[TCA_CAKE_NAT]);
>> +       }
>
>
> I think it's better to return -EOPNOTSUPP when CONFIG_NF_CONNTRACK
> is not enabled.

Good point, will fix :)

-Toke

  reply	other threads:[~2018-05-16 21:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 20:29 [Cake] [PATCH net-next v12 0/7] sched: Add Common Applications Kept Enhanced (cake) qdisc Toke Høiland-Jørgensen
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 7/7] sch_cake: Conditionally split GSO segments Toke Høiland-Jørgensen
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 4/7] sch_cake: Add NAT awareness to packet classifier Toke Høiland-Jørgensen
2018-05-16 20:56   ` Cong Wang
2018-05-16 21:14     ` Toke Høiland-Jørgensen [this message]
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 2/7] sch_cake: Add ingress mode Toke Høiland-Jørgensen
2018-05-16 21:09   ` Cong Wang
2018-05-16 21:16     ` Toke Høiland-Jørgensen
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 5/7] sch_cake: Add DiffServ handling Toke Høiland-Jørgensen
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 1/7] sched: Add Common Applications Kept Enhanced (cake) qdisc Toke Høiland-Jørgensen
2018-05-16 20:44   ` Cong Wang
2018-05-16 21:13     ` Toke Høiland-Jørgensen
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 3/7] sch_cake: Add optional ACK filter Toke Høiland-Jørgensen
2018-05-17 11:04   ` Eric Dumazet
2018-05-17 11:23     ` Toke Høiland-Jørgensen
2018-05-17 11:56       ` Eric Dumazet
2018-05-17 13:11         ` Toke Høiland-Jørgensen
2018-05-18  2:36           ` Ryan Mounce
2018-05-18  4:08             ` Eric Dumazet
2018-05-18  7:43               ` Ryan Mounce
2018-05-18  4:27       ` Cong Wang
2018-05-18 11:18         ` Kevin Darbyshire-Bryant
2018-05-18 11:23           ` Sebastian Moeller
2018-05-18 15:20           ` Eric Dumazet
2018-05-16 20:29 ` [Cake] [PATCH net-next v12 6/7] sch_cake: Add overhead compensation support to the rate shaper Toke Høiland-Jørgensen

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=87o9hfuwu3.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@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