From: wenxu
Only the nat_action in the nat_action_info is used for conn
packet forward and other item such as min/max_ip/port only
used for the new conn operation. So the whole nat_ction_info
no need store in conn. This will also avoid unnecessary memory
allocation.
Signed-off-by: wenxu
---
l
nat_info->nat_action
On Wed, Aug 4, 2021 at 11:20 PM wrote:
>
> From: wenxu
>
> Only the nat_action in the nat_action_info is used for conn
> packet forward and other item such as min/max_ip/port only
> used for the new conn operation. So the whole nat_ction_info
> no need store in conn. This wi
From: Michael Santana
Date: 2021-08-09 23:17:06
To: we...@ucloud.cn
Cc: b...@ovn.org,Ilya Maximets
,dlu...@gmail.com,d...@openvswitch.org
Subject: Re: [ovs-dev] [PATCH] conntrack: remove the nat_action_info from the
conn>nat_info->nat_action
>
>On Wed, Aug 4, 2021 at 11:
On Mon, Aug 9, 2021 at 11:41 PM wenxu wrote:
>
>
>
>
>
>
>
>
> From: Michael Santana
> Date: 2021-08-09 23:17:06
> To: we...@ucloud.cn
> Cc: b...@ovn.org,Ilya Maximets
> ,dlu...@gmail.com,d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] conn
On Thu, Aug 5, 2021, at 05:11, we...@ucloud.cn wrote:
> From: wenxu
Hi Wenxu,
A few nits in the commit log, otherwise the change looks good to me.
>
> Only the nat_action in the nat_action_info is used for conn
> packet forward and other item such as min/max_ip/port only
> used for the new co
