ffd64df9d3
This is an effective revert of: I312a950131d62d93fb4bc121bc5e60febb8d35ee "ovn: use stateless NAT rules for FIPs". The performance benefits promised by the "reverted" patch never materialized. On the contrary, the discussion in [1] revealed that the switch to stateless=true made it impossible to fully hw offload nat rules, while it's possible with stateless=false. Specifically, see this comment [2]. Since at this point it's unclear if keeping stateless=true as an option is beneficial for any case, even when w/o hw offload, and to avoid complexity of introducing a config option for unclear benefit, this patch reverts the effects of the original patch, switching all dnat_and_snat objects to implicit stateless=false state. This patch cannot be a clean revert because of the need for db migration. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2004995 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2004995#c18 Change-Id: I9e6e05b7a4f36383a44bd80f07d25052b17bdfa0
9 lines
262 B
YAML
9 lines
262 B
YAML
---
|
|
other:
|
|
- |
|
|
OVN driver reverted to using stateful NAT for floating IP implementation.
|
|
The previous switch to stateless didn't materialize the expected
|
|
performance benefits and instead introduced problems with potential
|
|
hardware offloading.
|
|
|