Hi Volodymyr,
Volodymyr Bendiuga <[email protected]> writes:
> Hi Andrew,
>
> I have tested the approach you wrote in previous mails, the one
> with setting next.mac to address we are looking for -1. It seems
> to be as slow as the original implementation, unfortunately.
Hum, that is what I was expecting... The ATU GetNext operation
(alongside an ether_addr_equal() call) should be quite fast.
> We use 6097 and 6352 chips, and both of them can not do any port
> filtering in hardware for fdb dump operation. Seems like they would
> benefit from cache. But I am not sure about other switches.
>
> Does anyone know about such feature in other switches?
Marvell switches cannot filter ATU entries for a specific port, they
contain a port vector.
I guess Florian might answer for Broadcom switches, and John might
answer for Qualcomm switches.
In all cases *if caching is really needed*, I think it won't hurt to do
it in DSA core even if a switch support FDB dump operations on a
per-port basis, as Andrew mentioned.
Thanks,
Vivien
