From: "Nambiar, Amritha" <amritha.nambiar@intel.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
jeffrey.t.kirsher@intel.com, jiri@resnulli.us,
alexander.h.duyck@intel.com
Subject: Re: [PATCH net] i40e: flower: check if TC offload is enabled on a netdev
Date: Tue, 23 Jan 2018 01:10:18 -0800 [thread overview]
Message-ID: <173046db-9ec7-b1bf-5247-ed1ebe23e86f@intel.com> (raw)
In-Reply-To: <20180123080840.768-1-jakub.kicinski@netronome.com>
On 1/23/2018 12:08 AM, Jakub Kicinski wrote:
> Since TC block changes drivers are required to check if
> the TC hw offload flag is set on the interface themselves.
>
> Fixes: 2f4b411a3d67 ("i40e: Enable cloud filters via tc-flower")
> Fixes: 44ae12a768b7 ("net: sched: move the can_offload check from binding phase to rule insertion phase")
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Simon Horman <simon.horman@netronome.com>
Acked-by: Amritha Nambiar <amritha.nambiar@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
> index 42dcaefc4c19..af792112a2d3 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_main.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c
> @@ -7505,6 +7505,8 @@ static int i40e_setup_tc_cls_flower(struct i40e_netdev_priv *np,
> {
> struct i40e_vsi *vsi = np->vsi;
>
> + if (!tc_can_offload(vsi->netdev))
> + return -EOPNOTSUPP;
> if (cls_flower->common.chain_index)
> return -EOPNOTSUPP;
>
>
next prev parent reply other threads:[~2018-01-23 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 8:08 [PATCH net] i40e: flower: check if TC offload is enabled on a netdev Jakub Kicinski
2018-01-23 8:26 ` Jiri Pirko
2018-01-23 9:10 ` Nambiar, Amritha [this message]
2018-01-23 16:47 ` Jeff Kirsher
2018-01-24 21:51 ` 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=173046db-9ec7-b1bf-5247-ed1ebe23e86f@intel.com \
--to=amritha.nambiar@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.