All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: wenxu@ucloud.cn
Cc: paulb@mellanox.com, netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] net/sched: act_ct: add nat mangle action only for NAT-conntrack
Date: Fri, 29 May 2020 14:56:50 -0300	[thread overview]
Message-ID: <20200529175650.GF74252@localhost.localdomain> (raw)
In-Reply-To: <1590725265-17136-1-git-send-email-wenxu@ucloud.cn>

On Fri, May 29, 2020 at 12:07:45PM +0800, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
> 
> Currently add nat mangle action with comparing invert and ori tuple.
> It is better to check IPS_NAT_MASK flags first to avoid non necessary
> memcmp for non-NAT conntrack.
> 
> Signed-off-by: wenxu <wenxu@ucloud.cn>
> ---
>  net/sched/act_ct.c | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/net/sched/act_ct.c b/net/sched/act_ct.c
> index c50a86a..d621152 100644
> --- a/net/sched/act_ct.c
> +++ b/net/sched/act_ct.c
> @@ -198,18 +198,21 @@ static int tcf_ct_flow_table_add_action_nat(struct net *net,
>  					    struct flow_action *action)
>  {
>  	const struct nf_conntrack_tuple *tuple = &ct->tuplehash[dir].tuple;
> +	bool nat = ct->status & IPS_NAT_MASK;
>  	struct nf_conntrack_tuple target;

[A]

>  
>  	nf_ct_invert_tuple(&target, &ct->tuplehash[!dir].tuple);
>  
>  	switch (tuple->src.l3num) {
>  	case NFPROTO_IPV4:
> -		tcf_ct_flow_table_add_action_nat_ipv4(tuple, target,
> -						      action);
> +		if (nat)

Why do the same check multiple times, on all actions? As no other
action is performed if not doing a nat, seems at [A] above, it could
just:

if (!nat)
	return 0;

> +			tcf_ct_flow_table_add_action_nat_ipv4(tuple, target,
> +							      action);
>  		break;
>  	case NFPROTO_IPV6:
> -		tcf_ct_flow_table_add_action_nat_ipv6(tuple, target,
> -						      action);
> +		if (nat)
> +			tcf_ct_flow_table_add_action_nat_ipv6(tuple, target,
> +							      action);
>  		break;
>  	default:
>  		return -EOPNOTSUPP;
> @@ -217,10 +220,14 @@ static int tcf_ct_flow_table_add_action_nat(struct net *net,
>  
>  	switch (nf_ct_protonum(ct)) {
>  	case IPPROTO_TCP:
> -		tcf_ct_flow_table_add_action_nat_tcp(tuple, target, action);
> +		if (nat)
> +			tcf_ct_flow_table_add_action_nat_tcp(tuple, target,
> +							     action);
>  		break;
>  	case IPPROTO_UDP:
> -		tcf_ct_flow_table_add_action_nat_udp(tuple, target, action);
> +		if (nat)
> +			tcf_ct_flow_table_add_action_nat_udp(tuple, target,
> +							     action);
>  		break;
>  	default:
>  		return -EOPNOTSUPP;
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2020-05-29 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  4:07 [PATCH] net/sched: act_ct: add nat mangle action only for NAT-conntrack wenxu
2020-05-29 17:56 ` Marcelo Ricardo Leitner [this message]
2020-05-30  0:04   ` wenxu
2020-05-30  5:58     ` wenxu

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=20200529175650.GF74252@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=paulb@mellanox.com \
    --cc=wenxu@ucloud.cn \
    /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.