From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, marcelo.leitner@gmail.com,
jiri@resnulli.us, wenxu@ucloud.cn, saeedm@mellanox.com,
paulb@mellanox.com, gerlitz.or@gmail.com
Subject: Re: [PATCH net 0/2] flow_offload hardware priority fixes
Date: Mon, 5 Aug 2019 12:04:39 -0700 [thread overview]
Message-ID: <20190805120439.40d70cee@cakuba.netronome.com> (raw)
In-Reply-To: <20190803070854.zb3nvwj4ubx2mzy6@salvia>
On Sat, 3 Aug 2019 09:08:54 +0200, Pablo Neira Ayuso wrote:
> The idea is that every subsystem (ethtool, tc, nf) sets up/binds its
> own flow_block object. And each flow_block object has its own priority
> range space. So whatever priority the user specifies only applies to
> the specific subsystem.
Right, okay so that part is pretty obvious but thanks for spelling it
out.
Are you also agreeing that priorities of blocks, not rules within
a block are dictated by the order of processing within the kernel?
IOW TC blocks are _always_ before nft blocks?
> Drivers still need to be updated to support for more than one
> flow_block/subsystem binding at this stage though.
next prev parent reply other threads:[~2019-08-05 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 11:28 [PATCH net 0/2] flow_offload hardware priority fixes Pablo Neira Ayuso
2019-08-01 11:28 ` [PATCH net 1/2] net: sched: use major priority number as hardware priority Pablo Neira Ayuso
2019-08-01 11:28 ` [PATCH net 2/2,v3] netfilter: nf_tables: map basechain priority to " Pablo Neira Ayuso
2019-08-02 0:20 ` [PATCH net 0/2] flow_offload hardware priority fixes Jakub Kicinski
2019-08-02 11:00 ` Pablo Neira Ayuso
2019-08-02 20:47 ` Jakub Kicinski
2019-08-02 22:04 ` Pablo Neira Ayuso
2019-08-02 22:25 ` Jakub Kicinski
2019-08-03 7:08 ` Pablo Neira Ayuso
2019-08-05 19:04 ` Jakub Kicinski [this message]
2019-08-06 9:42 ` Pablo Neira Ayuso
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=20190805120439.40d70cee@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jiri@resnulli.us \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).