[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190808.184454.1230954896965640540.davem@davemloft.net>
Date: Thu, 08 Aug 2019 18:44:54 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: wenxu@...oud.cn
Cc: jakub.kicinski@...ronome.com, pablo@...filter.org,
netfilter-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v7 0/6] flow_offload: add indr-block in
nf_table_offload
From: wenxu@...oud.cn
Date: Wed, 7 Aug 2019 09:13:48 +0800
> 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 fifth 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.
>
> This version add a mutex lock for add/del flow_indr_block_ing_cb
Series applied, thank you.
Powered by blists - more mailing lists