[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190731192135.GA2324@nanopsycho>
Date: Wed, 31 Jul 2019 21:21:35 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: wenxu@...oud.cn
Cc: pablo@...filter.org, fw@...len.de, jakub.kicinski@...ronome.com,
netfilter-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/6] flow_offload: add indr-block in
nf_table_offload
Wed, Jul 31, 2019 at 10:12:27AM CEST, wenxu@...oud.cn wrote:
>From: wenxu <wenxu@...oud.cn>
>
>This series patch make nftables offload support the vlan and
>tunnel device offload through indr-block architecture.
>
>The first four patches mv tc indr block to flow offload and
>rename to flow-indr-block.
>Because the new flow-indr-block can't get the tcf_block
>directly. The fifthe patch provide a callback list to get
>flow_block of each subsystem immediately when the device
>register and contain a block.
>The last patch make nf_tables_offload support flow-indr-block.
>
>wenxu (6):
> cls_api: modify the tc_indr_block_ing_cmd parameters.
> cls_api: replace block with flow_block in tc_indr_block_dev
> cls_api: add flow_indr_block_call function
> flow_offload: move tc indirect block to flow offload
> flow_offload: support get flow_block immediately
> netfilter: nf_tables_offload: support indr block call
Wenxu, this is V5. Please repost is as V5. Also please provide per-patch
changelog, as you did with the previous versions. Thanks!
Powered by blists - more mailing lists