From: Simon Horman <horms@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>
Subject: Re: [iwl-net v1 1/2] ice: tc: check src_vsi in case of traffic from VF
Date: Tue, 19 Mar 2024 11:36:49 +0000 [thread overview]
Message-ID: <20240319113649.GG185808@kernel.org> (raw)
In-Reply-To: <20240315110821.511321-2-michal.swiatkowski@linux.intel.com>
On Fri, Mar 15, 2024 at 12:08:20PM +0100, Michal Swiatkowski wrote:
> In case of traffic going from the VF (so ingress for port representor)
> source VSI should be consider during packet classification. It is
> needed for hardware to not match packets from different ports with
> filters added on other port.
>
> It is only for "from VF" traffic, because other traffic direction
> doesn't have source VSI.
>
> Set correct ::src_vsi in rule_info to pass it to the hardware filter.
>
> For example this rule should drop only ipv4 packets from eth10, not from
> the others VF PRs. It is needed to check source VSI in this case.
> $tc filter add dev eth10 ingress protocol ip flower skip_sw action drop
>
> Fixes: 0d08a441fb1a ("ice: ndo_setup_tc implementation for PF")
> Reviewed-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-03-19 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 11:08 [iwl-net v1 0/2] ice: two fixes for tc code Michal Swiatkowski
2024-03-15 11:08 ` [iwl-net v1 1/2] ice: tc: check src_vsi in case of traffic from VF Michal Swiatkowski
2024-03-19 11:36 ` Simon Horman [this message]
2024-04-12 6:37 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2024-03-15 11:08 ` [iwl-net v1 2/2] ice: tc: allow zero flags in parsing tc flower Michal Swiatkowski
2024-03-19 11:36 ` Simon Horman
2024-04-12 6:38 ` [Intel-wired-lan] " Buvaneswaran, Sujai
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=20240319113649.GG185808@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.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 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).