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: Fri, 2 Aug 2019 15:25:49 -0700 [thread overview]
Message-ID: <20190802152549.357784a7@cakuba.netronome.com> (raw)
In-Reply-To: <20190802220409.klwdkcvjgegz6hj2@salvia>
On Sat, 3 Aug 2019 00:04:09 +0200, Pablo Neira Ayuso wrote:
> That patch removed the reference to tcf_auto_prio() already, please
> let me know if you have any more specific update you would like to see
> on that patch.
Please explain why the artificial priorities are needed at all.
Hardware should order tables based on table type - ethtool, TC, nft.
As I mentioned in the first email, and unless you can make a strong
case against that.
Within those tables we should follow the same ordering rules as we
do in software (modulo ethtool but ordering is pretty clear there).
next prev parent reply other threads:[~2019-08-02 22:26 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 [this message]
2019-08-03 7:08 ` Pablo Neira Ayuso
2019-08-05 19:04 ` Jakub Kicinski
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=20190802152549.357784a7@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).