From: Jiri Pirko <jiri@resnulli.us>
To: wenxu <wenxu@ucloud.cn>
Cc: pablo@netfilter.org, fw@strlen.de, jakub.kicinski@netronome.com,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload
Date: Mon, 29 Jul 2019 15:13:10 +0200 [thread overview]
Message-ID: <20190729131310.GG2211@nanopsycho> (raw)
In-Reply-To: <c218d9bb-1da7-2ed6-d5b0-afddbe3d0bd7@ucloud.cn>
Mon, Jul 29, 2019 at 02:47:07PM CEST, wenxu@ucloud.cn wrote:
>
>在 2019/7/29 19:13, Jiri Pirko 写道:
>> Sun, Jul 28, 2019 at 08:52:47AM CEST, 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>
>>> ---
>>> v3: subsys_initcall for init_flow_indr_rhashtable
>>> v4: no change
>>>
>> [...]
>>
>>
>>> 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;
>>> +};
>> I don't understand why are you pushing this struct out of the c file to
>> the header. Please don't.
>>
>>
>>> +
>>> +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;
>> I don't understand why are you pushing this struct out of the c file to
>> the header. Please don't.
>
>the flow_indr_block_dev and indr_block_cb in the h file used for the function
You don't need it, same as before. Please don't expose this struct.
>
>tc_indr_block_ing_cmd in cls_api.c
>
>>> -static void tc_indr_block_ing_cmd(struct tc_indr_block_dev *indr_dev,
>>> - struct tc_indr_block_cb *indr_block_cb,
>>> +static void tc_indr_block_ing_cmd(struct net_device *dev,
>> I don't understand why you change struct tc_indr_block_dev * to
>> struct net_device * here. If you want to do that, please do that in a
>> separate patch, not it this one where only "the move" should happen.
Did you see the rest of my comments???
>>
next prev parent reply other threads:[~2019-07-29 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:52 [PATCH net-next v4 0/3] flow_offload: add indr-block in nf_table_offload wenxu
2019-07-28 6:52 ` [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload wenxu
2019-07-29 11:13 ` Jiri Pirko
2019-07-29 12:47 ` wenxu
2019-07-29 13:13 ` Jiri Pirko [this message]
2019-07-29 11:15 ` Jiri Pirko
2019-07-28 6:52 ` [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately wenxu
2019-07-28 20:16 ` Jakub Kicinski
2019-07-29 2:43 ` wenxu
2019-07-29 4:42 ` Jakub Kicinski
2019-07-29 7:05 ` wenxu
2019-07-29 16:51 ` Jakub Kicinski
2019-07-29 7:18 ` wenxu
2019-07-29 16:55 ` Jakub Kicinski
2019-07-30 0:10 ` wenxu
2019-07-28 6:52 ` [PATCH net-next v4 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=20190729131310.GG2211@nanopsycho \
--to=jiri@resnulli.us \
--cc=fw@strlen.de \
--cc=jakub.kicinski@netronome.com \
--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