Messages in this thread | ![/](/images/icornerl.gif) | | From | "Wang, Wei W" <> | Subject | RE: [PATCH v6 5/5] KVM: selftests: Allowing running dirty_log_perf_test on specific CPUs | Date | Fri, 28 Oct 2022 02:11:11 +0000 |
| |
On Friday, October 28, 2022 4:03 AM, Vipin Sharma wrote: > pthread_create() will internally call sched_setaffinity() syscall after creation of a > thread on a random CPU. So, from the performance side there is not much > difference between the two approaches.
The main difference I see is that the vcpu could be created on one NUMA node by default initially and then gets pinned to another NUMA node.
> > However, we will still need pin_this_task_to_pcpu()/sched_affinity() > to move the main thread to a specific pCPU, therefore, I am thinking of keeping > the current approach unless there is a strong objection to it.
I also don’t have strong objections, and it's up to you for now. I will re-visit this later after the code consolidation patchset is landed and see how this could be better consolidated from all user's perspective.
| ![\](/images/icornerr.gif) |