On 11/11/2026 19:05, Dimitri Daskalakis wrote:
Changes in v4:
- Nimrod and sashiko pointed out that not reporting DISABLED for
tcp-data-split makes the feature look unsupported. This conflicted
with my attempt to block users from setting DISABLED, locally sashiko
found several scenarios where ring changes would get blocked.
Can you please share those scenarios?
I think blocking 'disabled' was the right direction. Allowing it doesn't
give users anything new, only a way to pin HW-GRO off, at the cost of
another dependency between the two knobs in mlx5e_fix_features().
We can still report 'disabled' when HW-GRO is supported but off.