Re: [PATCH 2/2] FT: Check mobility domain when sending RRB message to local managed BSS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If you have multiple interfaces in one single instance, you can save
multiple eloop iterations that call back to those interfaces' rx, if the
packet is multicast. I think the memory allocation, copy, linked-list op,
and eloop registration might take more time if we didn't compare?

For example, a tri-band device with mesh capability, there will be at least
2 backhauls and 3 fronthuals. Other features like guest network and
multiple SSID might have more interfaces involved, depends on their driver.

But I think you're right, we should not make the path more complicated.
Perhaps we should compare only if it's multicast? What are your thoughts
on this?

On 2019-12-14 23:59, M. Braun <michael-dev@xxxxxxxxxxxxx> wrote:
> While we can do this, it makes testing the mobility domain check in the
> network receive path more complicated. What is the relevant benefit of
> this change?


_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux