- Fixed not working NAT in container in case
ip_conntrack_disable_ve0module option is set
- Fixed data corruption with 3ware 7000 and 8000 controllers
- Improved performance on AMD NUMA boxes
Patch from Dmitry Mishin <firstname.lastname@example.org>
If ip_conntrack_disable_ve0 option is set, than it is impossible to use nat targets (DNAT, SNAT) inside Containers even if nat table is permitted for them and respective modules are loaded. This patch fixes above issue.
Fixed and tested by Konstantin Khlebnikov <email@example.com>.
Issue reported by Alec.
Patch from Alexandr Andreev <firstname.lastname@example.org>
[SCHEDULER] fix load_balance() behavior, when it's invoked on a busy PCPU.
Note: looks like it works, but not sure about any kind of performance any more. Now we can trust performance results for VE's with --cpus 1
Bugs #93544, #98868.
Patch from Konstantin Khlebnikov <email@example.com>
CPU frequency switch may be incorrect on some hardware.
Ondemand use queue_delayed_work_on call and suppose that it works correctly. Farsched schedule kernel threads on random cpu and timer event may called not on supposed cpu.
This leads to CPU frequency is set almost randomly.
Patch prepared by Kirill Shileev <firstname.lastname@example.org>
Solves the problem with data corruption with 3ware 7000 or 8000 on x86_64 with more then 4G.