diff options
author | Christian Borntraeger <borntraeger@linux.ibm.com> | 2025-09-04 13:39:27 +0200 |
---|---|---|
committer | Christian Borntraeger <borntraeger@linux.ibm.com> | 2025-09-08 11:12:39 +0200 |
commit | 352ccf890a3e91f58bc32503f9afdc161bc2c34a (patch) | |
tree | c9e0e220e16bf1eb50f87e60bd07081db6914945 /rust/kernel/alloc/allocator_test.rs | |
parent | 57d88f02eb4449d96dfee3af4b7cd4287998bdbd (diff) |
KVM: s390: improve interrupt cpu for wakeup
Turns out that picking an idle CPU for floating interrupts has some
negative side effects. The guest will keep the IO workload on its CPU
and rather use an IPI from the interrupt CPU instead of moving workload.
For example a guest with 2 vCPUs and 1 fio process might run that fio on
vcpu1. If after diag500 both vCPUs are idle then vcpu0 is woken up. The
guest will then do an IPI from vcpu0 to vcpu1.
So lets change the heuristics and prefer the last CPU that went to
sleep. This one is likely still in halt polling and can be woken up
quickly.
This patch shows significant improvements in terms of bandwidth or
cpu consumption for fio and uperf workloads and seems to be a net
win.
Link: https://lore.kernel.org/linux-s390/20250904113927.119306-1-borntraeger@linux.ibm.com/
Reviewed-by: Christoph Schlameuß <schlameuss@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Diffstat (limited to 'rust/kernel/alloc/allocator_test.rs')
0 files changed, 0 insertions, 0 deletions