From: wenxu <wenxu@ucloud.cn>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v4 0/4] netfilter: flowtable: add indr-block offload
Date: Fri, 17 Jan 2020 07:04:46 +0800 [thread overview]
Message-ID: <ff794ea0-11b7-51fa-0f9b-32481ec90e7a@ucloud.cn> (raw)
In-Reply-To: <1578996040-6413-1-git-send-email-wenxu@ucloud.cn>
Hi pablo,
How about this series? Expect for your feedback. Thanks.
BR
wenxu
在 2020/1/14 18:00, 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 just rebase to the nf-next.
>
> Pablo, please give me some feedback. If you feel this series is ok, please
> apply it. Thanks.
>
> 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 | 239 +++++++++++++++++++++++++++++++---
> 1 file changed, 222 insertions(+), 17 deletions(-)
>
prev parent reply other threads:[~2020-01-16 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 10:00 [PATCH nf-next v4 0/4] netfilter: flowtable: add indr-block offload wenxu
2020-01-14 10:00 ` [PATCH nf-next v4 1/4] netfilter: flowtable: add nf_flow_table_block_offload_init() wenxu
2020-01-14 10:00 ` [PATCH nf-next v4 2/4] netfilter: flowtable: add indr block setup support wenxu
2020-01-18 20:01 ` Pablo Neira Ayuso
2020-01-19 4:35 ` wenxu
2020-01-14 10:00 ` [PATCH nf-next v4 3/4] netfilter: flowtable: add tunnel match offload support wenxu
2020-01-14 10:00 ` [PATCH nf-next v4 4/4] netfilter: flowtable: add tunnel encap/decap action " wenxu
2020-01-16 23:04 ` wenxu [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=ff794ea0-11b7-51fa-0f9b-32481ec90e7a@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).