All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
	 dev@openvswitch.org, ovs-dev@openvswitch.org,
	 davem@davemloft.net,  kuba@kernel.org,
	 Eric Dumazet <edumazet@google.com>,
	 Paolo Abeni <pabeni@redhat.com>,
	 Pravin B Shelar <pshelar@ovn.org>,
	 Ilya Maximets <i.maximets@ovn.org>,
	 Florian Westphal <fw@strlen.de>
Subject: Re: [PATCHv2 net-next] openvswitch: switch to per-action label counting in conntrack
Date: Tue, 13 Aug 2024 13:57:31 -0400	[thread overview]
Message-ID: <f7t34n8cnlg.fsf@redhat.com> (raw)
In-Reply-To: <6b9347d5c1a0b364e88d900b29a616c3f8e5b1ca.1723483073.git.lucien.xin@gmail.com> (Xin Long's message of "Mon, 12 Aug 2024 13:17:53 -0400")

Xin Long <lucien.xin@gmail.com> writes:

> Similar to commit 70f06c115bcc ("sched: act_ct: switch to per-action
> label counting"), we should also switch to per-action label counting
> in openvswitch conntrack, as Florian suggested.
>
> The difference is that nf_connlabels_get() is called unconditionally
> when creating an ct action in ovs_ct_copy_action(). As with these
> flows:
>
>   table=0,ip,actions=ct(commit,table=1)
>   table=1,ip,actions=ct(commit,exec(set_field:0xac->ct_label),table=2)
>
> it needs to make sure the label ext is created in the 1st flow before
> the ct is committed in ovs_ct_commit(). Otherwise, the warning in
> nf_ct_ext_add() when creating the label ext in the 2nd flow will
> be triggered:
>
>    WARN_ON(nf_ct_is_confirmed(ct));
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
> ---

Reviewed-by: Aaron Conole <aconole@redhat.com>


  reply	other threads:[~2024-08-13 17:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 17:17 [PATCHv2 net-next] openvswitch: switch to per-action label counting in conntrack Xin Long
2024-08-13 17:57 ` Aaron Conole [this message]
2024-08-13 18:58 ` Florian Westphal
2024-08-16  2:20 ` patchwork-bot+netdevbpf
2025-02-24  9:01 ` Jianbo Liu
2025-02-24 19:55   ` Xin Long
2025-02-25  1:38     ` Jianbo Liu
2025-02-25 14:57       ` Xin Long
2025-03-02 18:22         ` Xin Long
2025-03-03  2:14           ` Jianbo Liu
2025-03-03 16:42             ` Xin Long
2025-03-04  1:20               ` Jianbo Liu
2025-03-04 17:10                 ` Xin Long
2025-03-03 10:56           ` Ilya Maximets
2025-03-03 16:38             ` Xin Long
2025-03-04 13:23               ` Ilya Maximets
2025-03-04 15:21                 ` Xin Long

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=f7t34n8cnlg.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ovs-dev@openvswitch.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.