From: wenxu@ucloud.cn
To: pablo@netfilter.org, fw@strlen.de
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next v3 0/3] flow_offload: add indr-block in nf_table_offload
Date: Fri, 26 Jul 2019 21:34:04 +0800 [thread overview]
Message-ID: <1564148047-6428-1-git-send-email-wenxu@ucloud.cn> (raw)
From: wenxu <wenxu@ucloud.cn>
This series patch make nftables offload support the vlan and
tunnel device offload through indr-block architecture.
The first patch 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 second patch provide a callback to get tcf_block
immediately when the device register and contain a ingress block.
The third patch make nf_tables_offload support flow-indr-block.
wenxu (3):
flow_offload: move tc indirect block to flow offload
flow_offload: support get tcf block immediately
netfilter: nf_tables_offload: support indr block call
drivers/net/ethernet/mellanox/mlx5/core/en_rep.c | 10 +-
.../net/ethernet/netronome/nfp/flower/offload.c | 10 +-
include/net/flow_offload.h | 43 ++++
include/net/pkt_cls.h | 35 ---
include/net/sch_generic.h | 3 -
net/core/flow_offload.c | 191 ++++++++++++++++
net/netfilter/nf_tables_offload.c | 128 +++++++++--
net/sched/cls_api.c | 245 ++++-----------------
8 files changed, 389 insertions(+), 276 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-07-26 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:34 wenxu [this message]
2019-07-26 13:34 ` [PATCH net-next v3 1/3] flow_offload: move tc indirect block to flow offload wenxu
2019-07-27 0:56 ` Jakub Kicinski
2019-07-27 8:05 ` wenxu
2019-07-26 13:34 ` [PATCH net-next v3 2/3] flow_offload: support get tcf block immediately wenxu
2019-07-27 0:52 ` Jakub Kicinski
2019-07-27 8:02 ` wenxu
2019-07-26 13:34 ` [PATCH net-next v3 3/3] netfilter: nf_tables_offload: support indr block call 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=1564148047-6428-1-git-send-email-wenxu@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--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