From: Aaron Conole <aconole@redhat•com>
To: Xin Long <lucien.xin@gmail•com>
Cc: network dev <netdev@vger•kernel.org>,
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>,
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>
Subject: Re: [PATCHv2 net-next 3/5] openvswitch: move key and ovs_cb update out of handle_fragments
Date: Thu, 09 Feb 2023 10:01:22 -0500 [thread overview]
Message-ID: <f7tzg9mg9x9.fsf@redhat.com> (raw)
In-Reply-To: <d7a2bbc1b84729d619f20446b51ab461b788adb6.1675810210.git.lucien.xin@gmail.com> (Xin Long's message of "Tue, 7 Feb 2023 17:52:08 -0500")
Xin Long <lucien.xin@gmail•com> writes:
> This patch has no functional changes and just moves key and ovs_cb update
> out of handle_fragments, and skb_clear_hash() and skb->ignore_df change
> into handle_fragments(), to make it easier to move the duplicate code
> from handle_fragments() into nf_conntrack_ovs later.
>
> Note that it changes to pass info->family to handle_fragments() instead
> of key for the packet type check, as info->family is set according to
> key->eth.type in ovs_ct_copy_action() when creating the action.
>
> Signed-off-by: Xin Long <lucien.xin@gmail•com>
> ---
Reviewed-by: Aaron Conole <aconole@redhat•com>
next prev parent reply other threads:[~2023-02-09 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 22:52 [PATCHv2 net-next 0/5] net: move more duplicate code of ovs and tc conntrack into nf_conntrack_ovs Xin Long
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 [this message]
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=f7tzg9mg9x9.fsf@redhat.com \
--to=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=lucien.xin@gmail$(echo .)com \
--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