I am happy to see this issue receiving some attention and second the
wish to see these patches be considered for further review and inclusion
in an upcoming release.
Overcommit is not as common in enterprise and single-tenant virtualized
environments as it is in multi-tenant environments, and frankly we have
We have been running an early copy of these patches in our lab and in a
small production node sample set both on3.2.0-rc4 and 3.3.0-rc6 for over
two weeks now with great success. With the heavy level of vCPU:pCPU
overcommit required for our situation, the patches are increasing
performance by an _order of magnitude_ on our E5645 and E5620 systems.
Looks like a good baseline on which to build the KVM
might need some handshake to prevent interference on the host
the PLE code.
Avi, Thanks for reviewing. True, it is sort of equivalent to PLE on
non PLE machine.
Can you please let us know if this series can be considered for next
OR do you still have some concerns that needs addressing.
I shall rebase patches to 3.3 and resend. (main difference would be
UNINLINE_SPIN_UNLOCK and jump label changes to use
static_key_true/false() usage instead of static_branch.)