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 0/2 net,v4] flow_offload hardware priority fixes
Date: Tue, 6 Aug 2019 11:41:27 -0700 [thread overview]
Message-ID: <20190806114127.54d9d029@cakuba.netronome.com> (raw)
In-Reply-To: <20190806160310.6663-1-pablo@netfilter.org>
On Tue, 6 Aug 2019 18:03:08 +0200, Pablo Neira Ayuso wrote:
> Hi,
>
> This patchset contains two updates for the flow_offload users:
>
> 1) Pass the major tc priority to drivers so they do not have to
> lshift it. This is a preparation patch for the fix coming in
> patch #2.
>
> 2) Set the hardware priority from the netfilter basechain priority,
> some drivers break when using the existing hardware priority
> number that is set to zero.
Seems reasonable, thanks.
next prev parent reply other threads:[~2019-08-06 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 16:03 [PATCH 0/2 net,v4] flow_offload hardware priority fixes Pablo Neira Ayuso
2019-08-06 16:03 ` [PATCH 1/2 net,v4] net: sched: use major priority number as hardware priority Pablo Neira Ayuso
2019-08-06 16:03 ` [PATCH 2/2 net,v4] netfilter: nf_tables: map basechain priority to " Pablo Neira Ayuso
2019-08-06 18:41 ` Jakub Kicinski [this message]
2019-08-09 19:37 ` [PATCH 0/2 net,v4] flow_offload hardware priority fixes David Miller
2019-08-09 19:57 ` David Miller
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=20190806114127.54d9d029@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).