From: zhengzucheng <zhengzucheng@huawei.com>
To: <peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<bristot@redhat.com>, <vschneid@redhat.com>, <oleg@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>, <mingo@kernel.org>,
<peterx@redhat.com>, <tj@kernel.org>, <longman@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [Question] Include isolated cpu to ensure that tasks are not scheduled to isolated cpu?
Date: Mon, 2 Sep 2024 09:56:51 +0800 [thread overview]
Message-ID: <3e68ccda-1606-9494-f57a-75be9668b83d@huawei.com> (raw)
In-Reply-To: <20240725120315.212428-1-zhengzucheng@huawei.com>
In a cpuset subsystem, cpuset.cpus contains isolated cpu and
non-isolated cpu.
Is there any way to ensure that the task runs only on the non-isolated cpus?
eg:
isolcpus=1, cpusete.cpus=0-7. It is found that some tasks are scheduled
to cpu1.
In addition, task run on isolated cpu cann't be scheduled to other cpu
in the future.
Thanks!
next prev parent reply other threads:[~2024-09-02 1:57 UTC|newest]
Thread overview: 19+ 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 ` zhengzucheng [this message]
2024-09-02 3:00 ` [Question] Include isolated cpu to ensure that tasks are not scheduled to isolated cpu? 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
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=3e68ccda-1606-9494-f57a-75be9668b83d@huawei.com \
--to=zhengzucheng@huawei.com \
--cc=bristot@redhat.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=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®