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,
przemyslaw.kitszel@intel.com, marcin.szycik@intel.com
Subject: Re: [Intel-wired-lan] [iwl-next v1] ice: add recipe priority check in search
Date: Mon, 21 Oct 2024 14:57:03 +0100 [thread overview]
Message-ID: <20241021135703.GK402847@kernel.org> (raw)
In-Reply-To: <20241011070328.45874-1-michal.swiatkowski@linux.intel.com>
On Fri, Oct 11, 2024 at 09:03:28AM +0200, Michal Swiatkowski wrote:
> The new recipe should be added even if exactly the same recipe already
> exists with different priority.
>
> Example use case is when the rule is being added from TC tool context.
> It should has the highest priority, but if the recipe already exists
> the rule will inherit it priority. It can lead to the situation when
> the rule added from TC tool has lower priority than expected.
>
> The solution is to check the recipe priority when trying to find
> existing one.
>
> Previous recipe is still useful. Example:
> RID 8 -> priority 4
> RID 10 -> priority 7
>
> The difference is only in priority rest is let's say eth + mac +
> direction.
>
> Adding ARP + MAC_A + RX on RID 8, forward to VF0_VSI
> After that IP + MAC_B + RX on RID 10 (from TC tool), forward to PF0
>
> Both will work.
>
> In case of adding ARP + MAC_A + RX on RID 8, forward to VF0_VSI
> ARP + MAC_A + RX on RID 10, forward to PF0.
>
> Only second one will match, but this is expected.
>
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
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,
przemyslaw.kitszel@intel.com, marcin.szycik@intel.com
Subject: Re: [iwl-next v1] ice: add recipe priority check in search
Date: Mon, 21 Oct 2024 14:57:03 +0100 [thread overview]
Message-ID: <20241021135703.GK402847@kernel.org> (raw)
In-Reply-To: <20241011070328.45874-1-michal.swiatkowski@linux.intel.com>
On Fri, Oct 11, 2024 at 09:03:28AM +0200, Michal Swiatkowski wrote:
> The new recipe should be added even if exactly the same recipe already
> exists with different priority.
>
> Example use case is when the rule is being added from TC tool context.
> It should has the highest priority, but if the recipe already exists
> the rule will inherit it priority. It can lead to the situation when
> the rule added from TC tool has lower priority than expected.
>
> The solution is to check the recipe priority when trying to find
> existing one.
>
> Previous recipe is still useful. Example:
> RID 8 -> priority 4
> RID 10 -> priority 7
>
> The difference is only in priority rest is let's say eth + mac +
> direction.
>
> Adding ARP + MAC_A + RX on RID 8, forward to VF0_VSI
> After that IP + MAC_B + RX on RID 10 (from TC tool), forward to PF0
>
> Both will work.
>
> In case of adding ARP + MAC_A + RX on RID 8, forward to VF0_VSI
> ARP + MAC_A + RX on RID 10, forward to PF0.
>
> Only second one will match, but this is expected.
>
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@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-10-21 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 7:03 [Intel-wired-lan] [iwl-next v1] ice: add recipe priority check in search Michal Swiatkowski
2024-10-11 7:03 ` Michal Swiatkowski
2024-10-21 13:57 ` Simon Horman [this message]
2024-10-21 13:57 ` Simon Horman
2024-10-24 7:54 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2024-10-24 7:54 ` Buvaneswaran, Sujai
2024-11-07 12:06 ` Buvaneswaran, Sujai
2024-11-07 12:06 ` Buvaneswaran, Sujai
2024-11-08 10:08 ` Michal Swiatkowski
2024-11-11 5:24 ` Buvaneswaran, Sujai
2024-11-11 5:24 ` 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=20241021135703.GK402847@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=marcin.szycik@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@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 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.