netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: wenxu@ucloud.cn
Cc: kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 2/2] net/sched: act_frag: add implict packet fragment support.
Date: Thu, 5 Nov 2020 05:14:45 -0300	[thread overview]
Message-ID: <20201105081445.GQ3837@localhost.localdomain> (raw)
In-Reply-To: <1604562747-14802-2-git-send-email-wenxu@ucloud.cn>

On Thu, Nov 05, 2020 at 03:52:27PM +0800, wenxu@ucloud.cn wrote:

We cross-posted :)
I think my comments on the v1 still applies, btw.

...
> This patch add support for a xmit hook to mirred, that gets executed before
> xmiting the packet. Then, when act_ct gets loaded, it configs that hook.
> The frag xmit hook maybe reused by other modules.
...
> --- a/include/net/act_api.h
> +++ b/include/net/act_api.h
> @@ -239,6 +239,29 @@ int tcf_action_check_ctrlact(int action, struct tcf_proto *tp,
>  			     struct netlink_ext_ack *newchain);
>  struct tcf_chain *tcf_action_set_ctrlact(struct tc_action *a, int action,
>  					 struct tcf_chain *newchain);
> +
> +#if IS_ENABLED(CONFIG_NET_ACT_FRAG)
> +int tcf_exec_frag_xmit_hook(struct sk_buff *skb, int (*xmit)(struct sk_buff *skb));
> +void tcf_set_frag_xmit_hook(void);
> +void tcf_clear_frag_xmit_hook(void);
> +bool tcf_frag_xmit_hook_enabled(void);

Now it's naming the hook after frag action, but it's meant to be
generic. It got confusing on what is local to act_frag or not due to
that.


  reply	other threads:[~2020-11-05  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  7:52 [PATCH v2 net-next 1/2] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-05  7:52 ` [PATCH v2 net-next 2/2] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-05  8:14   ` Marcelo Ricardo Leitner [this message]
2020-11-05 10:44     ` 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=20201105081445.GQ3837@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 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).