From: Xin Long <lucien.xin@gmail•com>
To: network dev <netdev@vger•kernel.org>, dev@openvswitch•org
Cc: davem@davemloft•net, kuba@kernel•org,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
Pravin B Shelar <pshelar@ovn•org>,
Jamal Hadi Salim <jhs@mojatatu•com>,
Cong Wang <xiyou.wangcong@gmail•com>,
Jiri Pirko <jiri@resnulli•us>,
Pablo Neira Ayuso <pablo@netfilter•org>,
Florian Westphal <fw@strlen•de>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>,
Ilya Maximets <i.maximets@ovn•org>,
Aaron Conole <aconole@redhat•com>
Subject: [PATCHv2 net-next 0/5] net: move more duplicate code of ovs and tc conntrack into nf_conntrack_ovs
Date: Tue, 7 Feb 2023 17:52:05 -0500 [thread overview]
Message-ID: <cover.1675810210.git.lucien.xin@gmail.com> (raw)
We've moved some duplicate code into nf_nat_ovs in:
"net: eliminate the duplicate code in the ct nat functions of ovs and tc"
This patchset addresses more code duplication in the conntrack of ovs
and tc then creates nf_conntrack_ovs for them, and four functions will
be extracted and moved into it:
nf_ct_handle_fragments()
nf_ct_skb_network_trim()
nf_ct_helper()
nf_ct_add_helper()
v1->v2:
- In patch 1/5, fix the wrong option name 'NF_NF_CONNTRACK' used in
net/openvswitch/Kconfig, found by kernel test robot.
Xin Long (5):
net: create nf_conntrack_ovs for ovs and tc use
net: extract nf_ct_skb_network_trim function to nf_conntrack_ovs
openvswitch: move key and ovs_cb update out of handle_fragments
net: sched: move frag check and tc_skb_cb update out of
handle_fragments
net: extract nf_ct_handle_fragments to nf_conntrack_ovs
include/net/netfilter/nf_conntrack.h | 4 +
net/netfilter/Kconfig | 3 +
net/netfilter/Makefile | 1 +
net/netfilter/nf_conntrack_helper.c | 98 ---------------
net/netfilter/nf_conntrack_ovs.c | 178 +++++++++++++++++++++++++++
net/openvswitch/Kconfig | 1 +
net/openvswitch/conntrack.c | 80 ++----------
net/sched/Kconfig | 1 +
net/sched/act_ct.c | 76 ++----------
9 files changed, 207 insertions(+), 235 deletions(-)
create mode 100644 net/netfilter/nf_conntrack_ovs.c
--
2.31.1
next reply other threads:[~2023-02-07 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 22:52 Xin Long [this message]
2023-02-07 22:52 ` [PATCHv2 net-next 1/5] net: create nf_conntrack_ovs for ovs and tc use Xin Long
2023-02-08 10:15 ` Simon Horman
2023-02-09 14:59 ` Aaron Conole
2023-02-07 22:52 ` [PATCHv2 net-next 2/5] net: extract nf_ct_skb_network_trim function to nf_conntrack_ovs Xin Long
2023-02-08 10:15 ` Simon Horman
2023-02-09 15:00 ` Aaron Conole
2023-02-07 22:52 ` [PATCHv2 net-next 3/5] openvswitch: move key and ovs_cb update out of handle_fragments Xin Long
2023-02-08 10:16 ` Simon Horman
2023-02-09 15:01 ` Aaron Conole
2023-02-07 22:52 ` [PATCHv2 net-next 4/5] net: sched: move frag check and tc_skb_cb " Xin Long
2023-02-08 10:16 ` Simon Horman
2023-02-07 22:52 ` [PATCHv2 net-next 5/5] net: extract nf_ct_handle_fragments to nf_conntrack_ovs Xin Long
2023-02-08 10:17 ` Simon Horman
2023-02-09 15:08 ` Aaron Conole
2023-02-10 6:21 ` [PATCHv2 net-next 0/5] net: move more duplicate code of ovs and tc conntrack into nf_conntrack_ovs Jakub Kicinski
2023-02-10 10:35 ` Florian Westphal
2023-02-11 0:30 ` patchwork-bot+netdevbpf
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=cover.1675810210.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail$(echo .)com \
--cc=aconole@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dev@openvswitch$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=i.maximets@ovn$(echo .)org \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=marcelo.leitner@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pablo@netfilter$(echo .)org \
--cc=pshelar@ovn$(echo .)org \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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