From: Chengming Zhou <zhouchengming@bytedance.com>
To: mingo@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,
bristot@redhat.com, vschneid@redhat.com, odin@uged.al
Cc: linux-kernel@vger.kernel.org, duanxiongchun@bytedance.com,
songmuchun@bytedance.com,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: [PATCH v3 0/2] sched/fair: optimize and simplify rq
Date: Thu, 26 May 2022 18:39:27 +0800 [thread overview]
Message-ID: <20220526103929.14976-1-zhouchengming@bytedance.com> (raw)
Hi,
This version is based on [1], which try to not put cfs_rqs in throttled_hierarchy
on the rq leaf_cfs_rq_list, simplify the leaf_cfs_rq_list maintenance and
optimize the periodic load decay.
Vincent suggested moving throttled_hierarchy() outside list_add_leaf_cfs_rq()
because the task will not be added in this case which is quite misleading.
When do that moving in propagate_entity_cfs_rq(), I found it has problem
with propagation upwards. So add the fix in the first patch to be easier
to backport, please see the details in its commit message.
[1] https://lore.kernel.org/all/20220427160544.40309-1-zhouchengming@bytedance.com/
Chengming Zhou (2):
sched/fair: fix propagate during synchronous attach/detach
sched/fair: optimize and simplify rq leaf_cfs_rq_list
kernel/sched/fair.c | 87 ++++++++++++---------------------------------
1 file changed, 22 insertions(+), 65 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-26 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 10:39 Chengming Zhou [this message]
2022-05-26 10:39 ` [PATCH v3 1/2] sched/fair: fix propagate during synchronous attach/detach Chengming Zhou
2022-05-30 7:31 ` Vincent Guittot
2022-05-26 10:39 ` [PATCH v3 2/2] sched/fair: optimize and simplify rq leaf_cfs_rq_list Chengming Zhou
2022-05-30 7:52 ` Vincent Guittot
2022-05-31 13:55 ` [External] " Chengming Zhou
2022-05-31 16:32 ` Vincent Guittot
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=20220526103929.14976-1-zhouchengming@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=duanxiongchun@bytedance.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=odin@uged.al \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songmuchun@bytedance.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®