From: wenxu <wenxu@ucloud.cn>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v5 0/4] netfilter: flowtable: add indr-block offload
Date: Tue, 3 Mar 2020 20:13:53 +0800 [thread overview]
Message-ID: <d6dd697b-d0dc-d6c6-2cfc-f836f1ac9d02@ucloud.cn> (raw)
In-Reply-To: <1582521775-25176-1-git-send-email-wenxu@ucloud.cn>
Hi pablo,
How about this series?
BR
wenxu
在 2020/2/24 13:22, wenxu@ucloud.cn 写道:
> From: wenxu <wenxu@ucloud.cn>
>
> This patch provide tunnel offload based on route lwtunnel.
> The first two patches support indr callback setup
> Then add tunnel match and action offload.
>
> This version modify the second patch: make the dev can bind with different
> flowtable and check the NF_FLOWTABLE_HW_OFFLOAD flags in
> nf_flow_table_indr_block_cb_cmd.
>
> wenxu (4):
> netfilter: flowtable: add nf_flow_table_block_offload_init()
> netfilter: flowtable: add indr block setup support
> netfilter: flowtable: add tunnel match offload support
> netfilter: flowtable: add tunnel encap/decap action offload support
>
> net/netfilter/nf_flow_table_offload.c | 233 ++++++++++++++++++++++++++++++++--
> 1 file changed, 219 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2020-03-03 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 5:22 [PATCH nf-next v5 0/4] netfilter: flowtable: add indr-block offload wenxu
2020-02-24 5:22 ` [PATCH nf-next v5 1/4] netfilter: flowtable: add nf_flow_table_block_offload_init() wenxu
2020-02-24 5:22 ` [PATCH nf-next v5 2/4] netfilter: flowtable: add indr block setup support wenxu
2020-02-24 5:22 ` [PATCH nf-next v5 3/4] netfilter: flowtable: add tunnel match offload support wenxu
2020-02-24 5:22 ` [PATCH nf-next v5 4/4] netfilter: flowtable: add tunnel encap/decap action " wenxu
2020-03-03 12:13 ` wenxu [this message]
2020-03-03 21:53 ` [PATCH nf-next v5 0/4] netfilter: flowtable: add indr-block offload Pablo Neira Ayuso
2020-03-04 12:54 ` wenxu
2020-03-15 21:28 ` Pablo Neira Ayuso
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=d6dd697b-d0dc-d6c6-2cfc-f836f1ac9d02@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).