netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
	marcelo.leitner@gmail.com, jiri@resnulli.us, wenxu@ucloud.cn,
	saeedm@mellanox.com, paulb@mellanox.com, gerlitz.or@gmail.com,
	jakub.kicinski@netronome.com
Subject: Re: [PATCH net,v5 0/2] flow_offload hardware priority fixes
Date: Sun, 18 Aug 2019 14:13:46 -0700 (PDT)	[thread overview]
Message-ID: <20190818.141346.2186153528065492905.davem@davemloft.net> (raw)
In-Reply-To: <20190816012410.31844-1-pablo@netfilter.org>

From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Fri, 16 Aug 2019 03:24:08 +0200

> 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.
> 
> v5: fix patch 2/2 to address a clang warning and to simplify
>     the priority mapping.

Series applied.

      parent reply	other threads:[~2019-08-18 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16  1:24 [PATCH net,v5 0/2] flow_offload hardware priority fixes Pablo Neira Ayuso
2019-08-16  1:24 ` [PATCH net,v5 1/2] net: sched: use major priority number as hardware priority Pablo Neira Ayuso
2019-08-16  1:24 ` [PATCH net,v5 2/2] netfilter: nf_tables: map basechain priority to " Pablo Neira Ayuso
2019-08-16 19:44   ` Jakub Kicinski
2019-08-18 21:13 ` David Miller [this message]

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=20190818.141346.2186153528065492905.davem@davemloft.net \
    --to=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=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).