From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
jakub.kicinski@netronome.com, jiri@resnulli.us,
marcelo.leitner@gmail.com, saeedm@mellanox.com, wenxu@ucloud.cn,
gerlitz.or@gmail.com, paulb@mellanox.com
Subject: [PATCH net-next 0/3,v2] flow_offload hardware priority fixes
Date: Fri, 2 Aug 2019 15:28:43 +0200 [thread overview]
Message-ID: <20190802132846.3067-1-pablo@netfilter.org> (raw)
Hi,
This patchset contains three updates for the flow_offload users:
1) Pass major tc priority to drivers so they do not have to
lshift it. This is a preparation patch for the fix coming in
patch 3/3.
2) Add a new structure to basechain objects to wrap the offload
data. This is another preparation patch for the fix coming in
patch 3/3.
3) Allocate priority field per rule from the commit path and
pass it on to drivers. Currently this is set to zero and
some drivers bail out with it, start by priority number 1
and allocate new priority from there on. The priority field
is limited to 8-bits at this stage for simplicity.
v2: address Jakub comments to not use the netfilter basechain
priority for this mapping.
Please, apply, thank you.
Pablo Neira Ayuso (3):
net: sched: use major priority number as hardware priority
netfilter: nf_tables_offload: add offload field to basechain
filter: nf_tables_offload: set priority field for rules
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 2 +-
drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c | 2 +-
drivers/net/ethernet/mscc/ocelot_flower.c | 12 ++------
.../net/ethernet/netronome/nfp/flower/qos_conf.c | 2 +-
drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c | 2 +-
include/net/netfilter/nf_tables.h | 14 ++++++---
include/net/netfilter/nf_tables_offload.h | 6 ++++
include/net/pkt_cls.h | 2 +-
net/netfilter/nf_tables_api.c | 2 +-
net/netfilter/nf_tables_offload.c | 34 +++++++++++++++++-----
10 files changed, 51 insertions(+), 27 deletions(-)
--
2.11.0
next reply other threads:[~2019-08-02 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 13:28 Pablo Neira Ayuso [this message]
2019-08-02 13:28 ` [PATCH net-next 1/3,v2] net: sched: use major priority number as hardware priority Pablo Neira Ayuso
2019-08-05 8:36 ` Jiri Pirko
2019-08-02 13:28 ` [PATCH net-next 2/3] netfilter: nf_tables_offload: add offload field to basechain Pablo Neira Ayuso
2019-08-02 13:28 ` [PATCH net-next 3/3] filter: nf_tables_offload: set priority field for rules Pablo Neira Ayuso
2019-08-02 20:48 ` [PATCH net-next 0/3,v2] flow_offload hardware priority fixes Jakub Kicinski
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=20190802132846.3067-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulb@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=wenxu@ucloud.cn \
/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).