From: Jiri Pirko <jiri@resnulli.us>
To: 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 0/6] flow_offload: add indr-block in nf_table_offload
Date: Wed, 31 Jul 2019 21:21:35 +0200 [thread overview]
Message-ID: <20190731192135.GA2324@nanopsycho> (raw)
In-Reply-To: <1564560753-32603-1-git-send-email-wenxu@ucloud.cn>
Wed, Jul 31, 2019 at 10:12:27AM CEST, wenxu@ucloud.cn wrote:
>From: wenxu <wenxu@ucloud.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!
prev parent reply other threads:[~2019-07-31 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 8:12 [PATCH net-next 0/6] flow_offload: add indr-block in nf_table_offload wenxu
2019-07-31 8:12 ` [PATCH net-next 1/6] cls_api: modify the tc_indr_block_ing_cmd parameters wenxu
2019-07-31 8:12 ` [PATCH net-next 2/6] cls_api: replace block with flow_block in tc_indr_block_dev wenxu
2019-07-31 8:12 ` [PATCH net-next 3/6] cls_api: add flow_indr_block_call function wenxu
2019-07-31 8:12 ` [PATCH net-next 4/6] flow_offload: move tc indirect block to flow offload wenxu
2019-07-31 8:12 ` [PATCH net-next 5/6] flow_offload: support get flow_block immediately wenxu
2019-07-31 8:12 ` [PATCH net-next 6/6] netfilter: nf_tables_offload: support indr block call wenxu
2019-07-31 19:21 ` Jiri Pirko [this message]
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=20190731192135.GA2324@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;
as well as URLs for NNTP newsgroup(s).