From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: wenxu@ucloud.cn
Cc: pablo@netfilter.org, fw@strlen.de,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/3] flow_offload: move tc indirect block to flow offload
Date: Fri, 26 Jul 2019 17:56:27 -0700 [thread overview]
Message-ID: <20190726175627.7c146f94@cakuba.netronome.com> (raw)
In-Reply-To: <1564148047-6428-2-git-send-email-wenxu@ucloud.cn>
On Fri, 26 Jul 2019 21:34:05 +0800, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
>
> move tc indirect block to flow_offload and rename
> it to flow indirect block.The nf_tables can use the
> indr block architecture.
>
> Signed-off-by: wenxu <wenxu@ucloud.cn>
> diff --git a/include/net/flow_offload.h b/include/net/flow_offload.h
> index 00b9aab..66f89bc 100644
> --- a/include/net/flow_offload.h
> +++ b/include/net/flow_offload.h
> @@ -4,6 +4,7 @@
> #include <linux/kernel.h>
> #include <linux/list.h>
> #include <net/flow_dissector.h>
> +#include <linux/rhashtable.h>
>
> struct flow_match {
> struct flow_dissector *dissector;
> @@ -366,4 +367,42 @@ static inline void flow_block_init(struct flow_block *flow_block)
> INIT_LIST_HEAD(&flow_block->cb_list);
> }
>
> +typedef int flow_indr_block_bind_cb_t(struct net_device *dev, void *cb_priv,
> + enum tc_setup_type type, void *type_data);
> +
> +struct flow_indr_block_cb {
> + struct list_head list;
> + void *cb_priv;
> + flow_indr_block_bind_cb_t *cb;
> + void *cb_ident;
> +};
> +
> +typedef void flow_indr_block_ing_cmd_t(struct net_device *dev,
> + struct flow_block *flow_block,
> + struct flow_indr_block_cb *indr_block_cb,
> + enum flow_block_command command);
> +
> +struct flow_indr_block_dev {
> + struct rhash_head ht_node;
> + struct net_device *dev;
> + unsigned int refcnt;
> + struct list_head cb_list;
> + flow_indr_block_ing_cmd_t *ing_cmd_cb;
> + struct flow_block *flow_block;
TC can only have one block per device. Now with nftables offload we can
have multiple blocks. Could you elaborate how this is solved?
> +};
next prev parent reply other threads:[~2019-07-27 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:34 [PATCH net-next v3 0/3] flow_offload: add indr-block in nf_table_offload wenxu
2019-07-26 13:34 ` [PATCH net-next v3 1/3] flow_offload: move tc indirect block to flow offload wenxu
2019-07-27 0:56 ` Jakub Kicinski [this message]
2019-07-27 8:05 ` wenxu
2019-07-26 13:34 ` [PATCH net-next v3 2/3] flow_offload: support get tcf block immediately wenxu
2019-07-27 0:52 ` Jakub Kicinski
2019-07-27 8:02 ` wenxu
2019-07-26 13:34 ` [PATCH net-next v3 3/3] netfilter: nf_tables_offload: support indr block call 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=20190726175627.7c146f94@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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