From: Paolo Abeni <pabeni@redhat.com>
To: Chad Monroe <chad@monroe.io>, Andrew Lunn <andrew@lunn.ch>
Cc: SAYANTAN NANDY <sayantann11@gmail.com>,
netdev@vger.kernel.org, lorenzo@kernel.org
Subject: Re: [PATCH net v4] net: airoha: keep PPE offload when NPU refuses flow stats
Date: Thu, 29 Oct 2026 12:02:01 +0100 [thread overview]
Message-ID: <c57f4474-93fc-4f7f-b016-dbaf7875f113@redhat.com> (raw)
In-Reply-To: <J3XqO9fJOEvpsUH9m_DyrV8wgQzdtZdfhE8KZHv9ejvVty51zjizvG-0nmYn8ZhTGRJnLq0OcEbX7l3DvpqFp8dFEYuWYVpV5ZRKnGXmGKc=@monroe.io>
On 10/25/26 16:25, Chad Monroe wrote:
> On Wednesday, October 21st, 2026 at 5:49 AM, Andrew Lunn <andrew@lunn.ch> wrote:
>
>> On Wed, Oct 21, 2026 at 03:34:23PM +0530, SAYANTAN NANDY wrote:
>>> From: Chad Monroe <chad@monroe.io>
>>>
>>> With flow stats enabled, PPE offload setup requests flow statistics
>>> from the NPU. If the running NPU firmware does not support flow
>>> counters, the request fails and the current setup path aborts PPE
>>> offload.
>>
>> Since this never worked, it is not a regression fix.
>>
>> Why not keep it KISS and report the firmware is too old and suggest
>> the firmware is updated?
>>
>> Can the driver do the firmware upgrade?
>>
>> Andrew
>>
>
> Hi Andrew,
>
> The NPU firmware bin is downloaded at each boot and is present in
> linux-firmware so no issue with keeping it up to date.
>
> The main reason for this change is to behave better when flags mismatch.
> Previously, loading a driver compiled with flow stats support enabled
> would silently fail to offload if the firmware didn't have support.
>
> I did not like this blind failure so figured it would be better to
> check what the firmware supports. If flow stats support is not present
> in the firmware at least we can still do offloading.
>
> The main question is whether Airoha will release variants of firmware
> with flow stats support disabled in the future, or if this flag will
> always remain enabled. If it's just an issue of old firmware (all new
> version will support it) then report + failure is sufficient.
I think the simpler approach would be better. If Airoha would release
such a firmware, _that_ would be a regression on their side.
/P
next prev parent reply other threads:[~2026-10-29 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 10:04 [PATCH net v4] net: airoha: keep PPE offload when NPU refuses flow stats SAYANTAN NANDY
2026-10-21 12:48 ` Andrew Lunn
2026-10-25 15:25 ` Chad Monroe
2026-10-25 22:52 ` Andrew Lunn
2026-10-26 7:31 ` Lorenzo Bianconi
2026-10-29 11:02 ` Paolo Abeni [this message]
2026-10-25 11:40 ` netdev-bot+sashiko
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=c57f4474-93fc-4f7f-b016-dbaf7875f113@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=chad@monroe.io \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sayantann11@gmail.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