From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
ovs-dev@openvswitch.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, pshelar@ovn.org,
i.maximets@ovn.org, aconole@redhat.com, fw@strlen.de
Subject: Re: [PATCHv2 net-next] openvswitch: switch to per-action label counting in conntrack
Date: Fri, 16 Aug 2024 02:20:34 +0000 [thread overview]
Message-ID: <172377483499.3093813.15327738618411609051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6b9347d5c1a0b364e88d900b29a616c3f8e5b1ca.1723483073.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Aug 2024 13:17:53 -0400 you wrote:
> 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:
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next] openvswitch: switch to per-action label counting in conntrack
https://git.kernel.org/netdev/net-next/c/fcb1aa5163b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-16 2:20 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
2024-08-13 18:58 ` Florian Westphal
2024-08-16 2:20 ` patchwork-bot+netdevbpf [this message]
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=172377483499.3093813.15327738618411609051.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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 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).