> I was measuring bridging/routing performance and noticed this.
> The current code runs the "all packet" type handlers before calling the
> bridge hook. If an application (like some DHCP clients) is using AF_PACKET,
> this means that each received packet gets run through the Berkeley Packet Filter
> code in sk_run_filter (slow).
I know we closed this out by saying that even though performance
sucks, we can't really apply this without breaking things.
What would be broken is if the DHCP client isn't specifying
a device ifindex when it binds the AF_PACKET socket. That
would be an easy way to fix this performance problem at the