Currently, individual ports are wrapped in a KMutex, which is locked on:
- Packet transmission
- Packet receipt
- Periodic UFT expiry
- Reconfiguration of user-driven network state: Firewall rules, NAT/External IPs, DHCP Params, ...
Performance-wise, what I'm most concerned about is the total shared lock between 1. and 2., although 3. has caused minor issues (#426). It would be worth spending some time thinking about how this overlap of locks can be minimised overall -- keeping in mind that we do need pairwise flow installation to both In/Out tables, shared TCP state, etc.
Currently, individual ports are wrapped in a
KMutex, which is locked on:Performance-wise, what I'm most concerned about is the total shared lock between 1. and 2., although 3. has caused minor issues (#426). It would be worth spending some time thinking about how this overlap of locks can be minimised overall -- keeping in mind that we do need pairwise flow installation to both In/Out tables, shared TCP state, etc.