Thread (9 messages) 9 messages, 2 authors, 9d ago

Re: [PATCH net-next 2/2] net: dsa: mv88e6xxx: use direct ATU hash on 88E6141/6341

From: Luke Howard <hidden>
Date: 2026-07-03 21:56:18
Also in: lkml

On 4 Jul 2026, at 7:43 am, Andrew Lunn [off-list ref] wrote:
quoted
No documentation, just my experience, which is why I asked in the
cover for others to test. I can include test results with the next
revision.
Not so much the test results, but the test case.

The reason i added the devlink option was because the network
contained only devices from one vendor. So the OUI in the MAC
addresses was the same, the usable number of bits in the MAC address
being cut in half, in the best case. As a result, there was a lot of
hash collisions. For this special case network, the test mode hash was
better.

If you are also seeing a lot of collisions, it makes me wounder what
your distribution of MAC addresses is.
Well, a bunch of unicast addresses along with MAAP for AVB.

But what triggered it was multiple FIDs (VLAN-aware bridge), which wouldn’t have been visible without the first patch to configure the ATU FID register correctly.

Luke
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help