From: zhengzucheng <zhengzucheng@huawei.com>
To: Waiman Long <longman@redhat.com>, <peterz@infradead.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
<oleg@redhat.com>, Frederic Weisbecker <frederic@kernel.org>,
<mingo@kernel.org>, <peterx@redhat.com>, <tj@kernel.org>,
<tjcao980311@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [Question] sched:the load is unbalanced in the VM overcommitment scenario
Date: Sat, 14 Sep 2024 10:15:47 +0800 [thread overview]
Message-ID: <672a45a5-722f-af57-dad4-a285acb0e53a@huawei.com> (raw)
In-Reply-To: <3fd8aa75-ce1b-4d5a-aada-0b2cfbedb36c@redhat.com>
在 2024/9/14 1:17, Waiman Long 写道:
> you don't actually need to use 2 different cpusets if they all get the
> same set of CPUs and memory nodes
Yes, you're right. The purpose of setting two different cpusets is to
simulate the scenario of two VMs.
each cpuset is a VM.
For example, the VM configuration is as follows:
<domain type='kvm' id='12676'>
<name>master</name>
<vcpu placement='static' cpuset='0-3,80-83'>8</vcpu>
<iothreads>1</iothreads>
<iothreadids>
<iothread id='1'/>
</iothreadids>
<cputune>
<vcpupin vcpu='0' cpuset='0-3,80-83'/>
<vcpupin vcpu='1' cpuset='0-3,80-83'/>
<vcpupin vcpu='2' cpuset='0-3,80-83'/>
<vcpupin vcpu='3' cpuset='0-3,80-83'/>
<vcpupin vcpu='4' cpuset='0-3,80-83'/>
<vcpupin vcpu='5' cpuset='0-3,80-83'/>
<vcpupin vcpu='6' cpuset='0-3,80-83'/>
<vcpupin vcpu='7' cpuset='0-3,80-83'/>
<emulatorpin cpuset='0-79'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='0'/>
<memnode cellid='0' mode='strict' nodeset='0'/>
</numatune>
next prev parent reply other threads:[~2024-09-14 2:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 12:03 [PATCH -next] sched/cputime: Fix mul_u64_u64_div_u64() precision for cputime Zheng Zucheng
2024-07-25 14:05 ` Peter Zijlstra
2024-07-25 14:49 ` zhengzucheng
2024-07-25 15:14 ` Peter Zijlstra
2024-07-26 2:32 ` [PATCH v2 " Zheng Zucheng
2024-07-26 10:44 ` Oleg Nesterov
2024-07-26 13:04 ` Oleg Nesterov
2024-07-26 13:08 ` Peter Zijlstra
2024-07-26 13:30 ` Oleg Nesterov
2024-07-30 6:55 ` Uwe Kleine-König
2024-07-29 10:34 ` [tip: sched/core] " tip-bot2 for Zheng Zucheng
2024-09-02 1:56 ` [Question] Include isolated cpu to ensure that tasks are not scheduled to isolated cpu? zhengzucheng
2024-09-02 3:00 ` Waiman Long
2024-09-13 4:03 ` [Question] sched:the load is unbalanced in the VM overcommitment scenario zhengzucheng
2024-09-13 15:55 ` Vincent Guittot
2024-09-14 7:03 ` zhengzucheng
2024-09-17 6:19 ` Vincent Guittot
2024-09-13 17:17 ` Waiman Long
2024-09-14 2:15 ` zhengzucheng [this message]
2024-09-13 9:13 zhengzucheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=672a45a5-722f-af57-dad4-a285acb0e53a@huawei.com \
--to=zhengzucheng@huawei.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=tjcao980311@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®