netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Blakey <paulb@nvidia.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: vladbu@nvidia.com
Subject: Re: [PATCH nf] sched: act_ct: additional checks for outdated flows
Date: Wed, 25 Oct 2023 10:32:11 +0300	[thread overview]
Message-ID: <0137b038-0007-8f25-1a15-48b023cb1ea9@nvidia.com> (raw)
In-Reply-To: <20231024200243.50784-1-pablo@netfilter.org>



On 24/10/2023 23:02, Pablo Neira Ayuso wrote:
> From: Vlad Buslov <vladbu@nvidia.com>
> 
> Current nf_flow_is_outdated() implementation considers any flow table flow
> which state diverged from its underlying CT connection status for teardown
> which can be problematic in the following cases:
> 
> - Flow has never been offloaded to hardware in the first place either
> because flow table has hardware offload disabled (flag
> NF_FLOWTABLE_HW_OFFLOAD is not set) or because it is still pending on 'add'
> workqueue to be offloaded for the first time. The former is incorrect, the
> later generates excessive deletions and additions of flows.
> 
> - Flow is already pending to be updated on the workqueue. Tearing down such
> flows will also generate excessive removals from the flow table, especially
> on highly loaded system where the latency to re-offload a flow via 'add'
> workqueue can be quite high.
> 
> When considering a flow for teardown as outdated verify that it is both
> offloaded to hardware and doesn't have any pending updates.
> 
> Fixes: 41f2c7c342d3 ("net/sched: act_ct: Fix promotion of offloaded unreplied tuple")
> Reviewed-by: Paul Blakey <paulb@nvidia.com>
> Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> I am taking Vlad's patch and rebasing as per his request:
> 
> This patch requires:
> https://patchwork.ozlabs.org/project/netfilter-devel/patch/20231024193815.1987-1-pablo@netfilter.org/
> 
>   net/sched/act_ct.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/net/sched/act_ct.c b/net/sched/act_ct.c
> index 0d44da4e8c8e..fb52d6f9aff9 100644
> --- a/net/sched/act_ct.c
> +++ b/net/sched/act_ct.c
> @@ -281,6 +281,8 @@ static int tcf_ct_flow_table_fill_actions(struct net *net,
>   static bool tcf_ct_flow_is_outdated(const struct flow_offload *flow)
>   {
>   	return test_bit(IPS_SEEN_REPLY_BIT, &flow->ct->status) &&
> +	       test_bit(IPS_HW_OFFLOAD_BIT, &flow->ct->status) &&
> +	       !test_bit(NF_FLOW_HW_PENDING, &flow->flags) &&
>   	       !test_bit(NF_FLOW_HW_ESTABLISHED, &flow->flags);
>   }
>   

Reviewed-by: Paul Blakey <paulb@nvidia.com>

      parent reply	other threads:[~2023-10-25  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 20:02 [PATCH nf] sched: act_ct: additional checks for outdated flows Pablo Neira Ayuso
2023-10-24 20:09 ` Vlad Buslov
2023-10-25  7:32 ` Paul Blakey [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0137b038-0007-8f25-1a15-48b023cb1ea9@nvidia.com \
    --to=paulb@nvidia.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=vladbu@nvidia.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;
as well as URLs for NNTP newsgroup(s).