From: wenxu@ucloud.cn
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH nf-next 0/4] netfilter: nf_flow_table_offload: support tunnel match
Date: Fri, 15 Nov 2019 20:03:26 +0800 [thread overview]
Message-ID: <1573819410-3685-1-git-send-email-wenxu@ucloud.cn> (raw)
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 patch is based on
http://patchwork.ozlabs.org/patch/1194247/
http://patchwork.ozlabs.org/patch/1195539/
wenxu (4):
netfilter: nf_flow_table_offload: refactor nf_flow_table_offload_setup
to support indir setup
netfilter: nf_flow_table_offload: add indr block setup support
netfilter: nf_flow_table_offload: add tunnel match offload support
netfilter: nf_flow_table_offload: add tunnel encap/decap action
offload support
net/netfilter/nf_flow_table_offload.c | 240 +++++++++++++++++++++++++++++++---
1 file changed, 223 insertions(+), 17 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-11-15 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 12:03 wenxu [this message]
2019-11-15 12:03 ` [PATCH nf-next 1/4] netfilter: nf_flow_table_offload: refactor nf_flow_table_offload_setup to support indir setup wenxu
2019-11-15 12:03 ` [PATCH nf-next 2/4] netfilter: nf_flow_table_offload: add indr block setup support wenxu
2019-11-15 12:03 ` [PATCH nf-next 3/4] netfilter: nf_flow_table_offload: add tunnel match offload support wenxu
2019-11-15 12:03 ` [PATCH nf-next 4/4] netfilter: nf_flow_table_offload: add tunnel encap/decap action " wenxu
2019-11-15 21:48 ` [PATCH nf-next 0/4] netfilter: nf_flow_table_offload: support tunnel match Pablo Neira Ayuso
2019-11-16 8:06 ` wenxu
2019-11-18 21:59 ` Pablo Neira Ayuso
2019-11-19 6:40 ` 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=1573819410-3685-1-git-send-email-wenxu@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).