From: wenxu <wenxu@ucloud.cn>
To: pablo@netfilter.org, fw@strlen.de
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v5 0/8] netfilter: nf_tables_offload: support tunnel offload
Date: Thu, 5 Sep 2019 12:08:18 +0800 [thread overview]
Message-ID: <e78d3b61-0e89-97aa-0008-c3cad2c9ac5d@ucloud.cn> (raw)
In-Reply-To: <1566364193-31330-1-git-send-email-wenxu@ucloud.cn>
Hi pablo,
Any comments for this series?
BR
wenxu
On 8/21/2019 1:09 PM, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
>
> This series add NFT_TUNNEL_IP/6_SRC/DST match and tunnel expr offload.
> Also add NFTA_TUNNEL_KEY_RELEASE actions adn objref, tunnel obj offload
>
> This version just split from the orignal big seriese without dependency
> with each other
>
> wenxu (8):
> netfilter: nft_tunnel: add nft_tunnel_mode_validate function
> netfilter: nft_tunnel: support NFT_TUNNEL_IP_SRC/DST match
> netfilter: nft_tunnel: add ipv6 check in nft_tunnel_mode_validate
> netfilter: nft_tunnel: support NFT_TUNNEL_IP6_SRC/DST match
> netfilter: nft_tunnel: support tunnel meta match offload
> netfilter: nft_tunnel: add NFTA_TUNNEL_KEY_RELEASE action
> netfilter: nft_objref: add nft_objref_type offload
> netfilter: nft_tunnel: support nft_tunnel_obj offload
>
> include/net/netfilter/nf_tables.h | 3 +
> include/net/netfilter/nf_tables_offload.h | 5 +
> include/uapi/linux/netfilter/nf_tables.h | 5 +
> net/netfilter/nft_objref.c | 14 +++
> net/netfilter/nft_tunnel.c | 159 +++++++++++++++++++++++++++---
> 5 files changed, 173 insertions(+), 13 deletions(-)
>
prev parent reply other threads:[~2019-09-05 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 5:09 [PATCH nf-next v5 0/8] netfilter: nf_tables_offload: support tunnel offload wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 1/8] netfilter: nft_tunnel: add nft_tunnel_mode_validate function wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 2/8] netfilter: nft_tunnel: support NFT_TUNNEL_IP_SRC/DST match wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 3/8] netfilter: nft_tunnel: add ipv6 check in nft_tunnel_mode_validate wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 4/8] netfilter: nft_tunnel: support NFT_TUNNEL_IP6_SRC/DST match wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 5/8] netfilter: nft_tunnel: support tunnel meta match offload wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 6/8] netfilter: nft_tunnel: add NFTA_TUNNEL_KEY_RELEASE action wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 7/8] netfilter: nft_objref: add nft_objref_type offload wenxu
2019-08-21 5:09 ` [PATCH nf-next v5 8/8] netfilter: nft_tunnel: support nft_tunnel_obj offload wenxu
2019-09-05 4:08 ` 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=e78d3b61-0e89-97aa-0008-c3cad2c9ac5d@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=fw@strlen.de \
--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).