From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Juri Lelli <juri.lelli@redhat.com>, Qais Yousef <qyousef@layalina.io>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Waiman Long <longman@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
tj@kernel.org, linux-kernel@vger.kernel.org,
luca.abeni@santannapisa.it, claudio@evidence.eu.com,
tommaso.cucinotta@santannapisa.it, bristot@redhat.com,
mathieu.poirier@linaro.org, cgroups@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Wei Wang <wvw@google.com>, Rick Yiu <rickyiu@google.com>,
Quentin Perret <qperret@google.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Zefan Li <lizefan.x@bytedance.com>,
linux-s390@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v3] sched: cpuset: Don't rebuild root domains on suspend-resume
Date: Mon, 13 Mar 2023 13:37:48 +0100 [thread overview]
Message-ID: <e81ffc13-a89e-d43e-18d1-10d9e0161638@arm.com> (raw)
In-Reply-To: <ZAhhGi55BkYkc3ss@localhost.localdomain>
On 08/03/2023 11:19, Juri Lelli wrote:
> On 01/03/23 17:03, Qais Yousef wrote:
>> On 03/01/23 15:26, Juri Lelli wrote:
>>> On 01/03/23 12:28, Qais Yousef wrote:
>>>> On 03/01/23 08:31, Juri Lelli wrote:
>>>
>>> ...
>>>
>>>>> Not ignoring you guys here, but it turns out I'm quite bogged down with
>>>>> other stuff at the moment. :/ So, apologies and I'll try to get to this
>>>>> asap. Thanks a lot for all your efforts and time reviewing so far!
>>>>
>>>> Np, I can feel you :-)
>>>
>>> Eh. :/
>>
>> I hope I did not offend. That was meant as no pressure, I understand.
>
> No offence at all! I meant "we are all on the same boat it seems". :)
>
>>> BTW, do you have a repro script of some sort handy I might play with?
>>
>> Sorry no. You'll just need to suspend to ram. I had a simple patch to measure
>> the time around the call and trace_printk'ed the result.
>>
>> I was working on a android phone which just suspends to ram if you turn the
>> screen off and disconnect the usb.
>
> Looks like I could come up with the following
>
> https://github.com/jlelli/linux.git deadline/rework-cpusets
> https://github.com/jlelli/linux/tree/deadline/rework-cpusets
>
> which I don't think it's at a point that I feel comfortable to propose
> as an RFC (not even sure if it actually makes sense), but it survived my
> very light testing.
>
> Could you please take a look and, if it makes some sense in theory, give
> it a try on your end?
sched/cpuset: Keep track of SCHED_DEADLINE task in cpusets
@@ -2474,6 +2494,11 @@ static int cpuset_can_attach(struct
cgroup_taskset *tset)
goto out_unlock;
}
+ if (dl_task(task)) {
+ cs->deadline_tasks++;
+ cpuset_attach_old_cs->deadline_tasks--;
+ }
+
This one looks odd. task is NULL here ?
If you move a DL task from one cpuset to another this happens now:
root@juno:~# ps2 | grep DLN
82 82 140 0 - DLN sugov:0
83 83 140 0 - DLN sugov:1
1615 1616 140 0 - DLN thread0-0
1615 1617 140 0 - DLN thread0-1
1615 1618 140 0 - DLN thread0-2
1615 1619 140 0 - DLN thread0-3
1615 1620 140 0 - DLN thread0-4
1615 1621 140 0 - DLN thread0-5
1615 1622 140 0 - DLN thread0-6
1615 1623 140 0 - DLN thread0-7
1615 1624 140 0 - DLN thread0-8
1615 1625 140 0 - DLN thread0-9
1615 1626 140 0 - DLN thread0-10
1615 1627 140 0 - DLN thread0-11 <--
root@juno:~# cd /sys/fs/cgroup/cpuset
root@juno:~# mkdir cs1
root@juno:~# echo 0 > cs1/cpuset.mems
root@juno:~# echo 0,3-5 > cs1/cpuset.cpus
root@juno:~# echo 1627 > cs1/tasks
root@juno:~# [ 154.968900] *** task=0000000000000000
[...]
next prev parent reply other threads:[~2023-03-13 12:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 22:14 [PATCH v3] sched: cpuset: Don't rebuild root domains on suspend-resume Qais Yousef
2023-02-23 15:38 ` Qais Yousef
2023-02-24 15:14 ` Dietmar Eggemann
2023-02-27 20:57 ` Qais Yousef
2023-02-28 14:09 ` Dietmar Eggemann
2023-02-28 17:46 ` Qais Yousef
2023-03-01 7:31 ` Juri Lelli
2023-03-01 12:28 ` Qais Yousef
2023-03-01 14:26 ` Juri Lelli
2023-03-01 17:03 ` Qais Yousef
2023-03-08 10:19 ` Juri Lelli
2023-03-08 18:01 ` Hao Luo
2023-03-09 6:55 ` Juri Lelli
2023-03-09 22:23 ` Hao Luo
2023-03-11 18:51 ` Qais Yousef
2023-03-13 16:37 ` Juri Lelli
2023-03-13 17:10 ` Dietmar Eggemann
2023-03-14 11:41 ` Dietmar Eggemann
2023-03-08 19:21 ` Waiman Long
2023-03-13 12:37 ` Dietmar Eggemann [this message]
2023-03-07 19:56 ` Hao Luo
2023-03-07 20:08 ` Waiman Long
2023-03-07 21:06 ` Hao Luo
2023-03-07 21:13 ` Waiman Long
2023-03-07 22:17 ` Hao Luo
2023-03-08 2:29 ` Waiman Long
2023-03-08 18:11 ` Hao Luo
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=e81ffc13-a89e-d43e-18d1-10d9e0161638@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=bristot@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=claudio@evidence.eu.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=luca.abeni@santannapisa.it \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=qyousef@layalina.io \
--cc=rickyiu@google.com \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=tj@kernel.org \
--cc=tommaso.cucinotta@santannapisa.it \
--cc=vincent.guittot@linaro.org \
--cc=wvw@google.com \
--cc=x86@kernel.org \
/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