On 7/31/2024 7:43 AM, Jakub Kicinski wrote:

On Wed, 31 Jul 2024 07:40:11 +0000 Song, Yoong Siang wrote:

quoted

Regarding your suggestion of implementing a "wildcard rule,"
are you suggesting the use of an ethtool command similar to the following?

ethtool -U <iface name> flow-type ether action <default queue>

I have a concern that users might be not aware that this nfc rule is having lowest priority,
as the default queue would only take effect when no other filtering rules match.

I believe that ethtool n-tuple rules are expected to be executed in
order. User can use the 'loc' argument to place the rule at the end 
of the table.

Yes. Some drivers lack support for ordered rules, but instead enforce
that no rule can be added if it would cause such a violation.

In this case, (I haven't dug into the actual patches or code), I suspect
the driver will need to validate the location values when adding rules
to ensure that all rules which don't use the default queue have higher
priority than the wild card rule. The request to add a filter should
reject the rule in the case where a default queue rule was added with a
higher priority location.

quoted

Do you see this as a potential issue? If not, I am willing to proceed with
exploring the ethtool options you've mentioned.