From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [patch net-next] iavf: use tc_cls_can_offload_basic() instead of chain check
Date: Tue, 25 Feb 2020 13:15:46 -0800 [thread overview]
Message-ID: <469b51add666cf3df7381b6409a3972c70024c12.camel@intel.com> (raw)
In-Reply-To: <20200225121023.6011-1-jiri@resnulli.us>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Tue, 2020-02-25 at 13:10 +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@mellanox.com>
>
> Looks like the iavf code actually experienced a race condition, when
> a
> developer took code before the check for chain 0 was put to helper.
> So use tc_cls_can_offload_basic() helper instead of direct check and
> move the check to _cb() so this is similar to i40e code.
>
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Go ahead and pick this up Dave, thanks!
> ---
> This was originally part of "net: allow user specify TC filter HW
> stats type"
> patchset, but it is no longer related after the requested changes.
> Sending separatelly.
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-25 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 12:10 [patch net-next] iavf: use tc_cls_can_offload_basic() instead of chain check Jiri Pirko
2020-02-25 19:13 ` David Miller
2020-02-25 21:15 ` Jeff Kirsher [this message]
2020-02-25 21:20 ` David Miller
2020-02-26 7:36 ` Jiri Pirko
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=469b51add666cf3df7381b6409a3972c70024c12.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).