Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics

[Nicolai Buchwitz]

Hi Paolo

On 27.8.2026 10:52, Paolo Abeni wrote:
> On 8/25/26 5:04 PM, Nicolai Buchwitz wrote:
> > Replying to netdev's sashiko
> > https://netdev-ai.bots.linux.dev/sashiko/#/message/20260824134703.766708-2-nb%40tipi-net.de:
>
> It looks like you instead replied to the comments from:
>
> https://sashiko.dev/#/patchset/20260824134703.766708-1-nb%40tipi-net.de
>
> Note that our reference saskiko instance is actually the one you
> pointed to above, even if the comments are at as slightly different
> URL:
>
> https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260824134703.766708-1-nb%40tipi-net.de

Thanks for the pointer. I'll have another look and check the findings.

Only partially related, but is there a good way to c&p the sashiko 
review already quoted, so
it is easier to respond inline via email? I saw the discussion about 
sending feedback via email
and also the note from Jakub in the 7.2 stats that the current false 
positive rate _might_
be stable enough to do this in the future, but until then this would 
help a lot!

> Also note that pre-existing issue should (usually) not be addressed
> in the same patchset (unless really bad/exploitable).

I've bundled patch 1 because patch 2 makes it far more visible. Happy to 
split out if you'd rather.

> Finally I have some concerns WRT patch 2/2: it should bring a
> significant performance regression, and the frames transmitted ATM are
> still valid (even if 'downgraded' csum wise). It would probably be good
> to provide some priv flag to enable/disable such behavior.

Agreed. I'm currently testing another approach that checks whether the 
checksum would be 0 and
only does the sw checksum calculation for those packets. Also, the 
testing from Alexander showed that
maybe not all revisions are affected. Théo can probably check Mobileye 
silicon so we can pin this down further.

> I guess some/most users would prefer send 1 frame out of 64K with csum
> validation unexpectedly disabled than hit a huge slowdown.

Agreed, lets see if the different approach might save us this at all.

> /P

Cheers
Nicolai