From: Honglei Wang <jameshongleiwang@126.com>
To: Chunxin Zang <spring.cxz@gmail.com>
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org,
Chen Yu <yu.c.chen@intel.com>,
yangchen11@lixiang.com, Jerry Zhou <zhouchunhua@lixiang.com>,
Chunxin Zang <zangchunxin@lixiang.com>,
mingo@redhat.com, Peter Zijlstra <peterz@infradead.org>,
juri.lelli@redhat.com, vincent.guittot@linaro.org
Subject: Re: [PATCH] sched/fair: Reschedule the cfs_rq when current is ineligible
Date: Tue, 11 Jun 2024 19:39:42 +0800 [thread overview]
Message-ID: <b596cb41-9c62-4134-a76d-6139ae859b07@126.com> (raw)
In-Reply-To: <DD2A2CD1-E7F9-4519-82F5-22E769364C55@gmail.com>
On 2024/6/6 20:39, Chunxin Zang wrote:
>
> Hi honglei
>
> Recently, I conducted testing of multiple cgroups using version 2. Version 2 ensures the
> RUN_TO_PARITY feature, so the test results are somewhat better under the
> NO_RUN_TO_PARITY feature.
> https://lore.kernel.org/lkml/20240529141806.16029-1-spring.cxz@gmail.com/T/
>
> The testing environment I used still employed 4 cores, 4 groups of hackbench (160 processes)
> and 1 cyclictest. If too many cgroups or processes are created on the 4 cores, the test
> results will fluctuate severely, making it difficult to discern any differences.
>
> The organization of cgroups was in two forms:
> 1. Within the same level cgroup, 10 sub-cgroups were created, with each cgroup having
> an average of 16 processes.
>
> EEVDF PATCH EEVDF-NO_PARITY PATCH-NO_PARITY
>
> LNICE(-19) # Avg Latencies: 00572 00347 00502 00218
>
> LNICE(0) # Avg Latencies: 02262 02225 02442 02321
>
> LNICE(19) # Avg Latencies: 03132 03422 03333 03489
>
> 2. In the form of a binary tree, 8 leaf cgroups were established, with a depth of 4.
> On average, each cgroup had 20 processes
>
> EEVDF PATCH EEVDF-NO_PARITY PATCH-NO_PARITY
>
> LNICE(-19) # Avg Latencies: 00601 00592 00510 00400
>
> LNICE(0) # Avg Latencies: 02703 02170 02381 02126
>
> LNICE(19) # Avg Latencies: 04773 03387 04478 03611
>
> Based on the test results, there is a noticeable improvement in scheduling latency after
> applying the patch in scenarios involving multiple cgroups.
>
>
> thanks
> Chunxin
>
Hi Chunxin,
Thanks for sharing the test result. It looks helpful at least in this
cgroups scenario. I'm still curious which point of the two changes helps
more in your test, just as mentioned at the very first mail of this thread.
Thanks,
Honglei
next prev parent reply other threads:[~2024-06-11 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:40 Chunxin Zang
2024-05-24 15:30 ` Chen Yu
2024-05-28 2:42 ` Chunxin Zang
2024-05-28 5:02 ` K Prateek Nayak
2024-05-28 7:18 ` Chunxin Zang
2024-05-28 7:47 ` K Prateek Nayak
2024-06-05 17:19 ` Chen Yu
2024-06-06 1:46 ` Chunxin Zang
2024-06-07 2:38 ` Chen Yu
2024-06-11 13:10 ` Chunxin Zang
2024-06-13 11:45 ` Chen Yu
2024-05-28 6:41 ` Chunxin Zang
2024-05-25 6:41 ` Mike Galbraith
2024-05-25 11:57 ` Chen Yu
2024-05-25 17:22 ` Mike Galbraith
2024-05-27 8:05 ` Peter Zijlstra
2024-05-27 9:53 ` Mike Galbraith
2024-05-25 11:48 ` Honglei Wang
[not found] ` <6AF97701-B8F4-46C6-851E-A8BACE97E8C0@gmail.com>
2024-06-03 2:55 ` Honglei Wang
2024-06-06 12:39 ` Chunxin Zang
2024-06-11 11:39 ` Honglei Wang [this message]
2024-05-29 6:06 ` kernel test robot
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=b596cb41-9c62-4134-a76d-6139ae859b07@126.com \
--to=jameshongleiwang@126.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=spring.cxz@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yangchen11@lixiang.com \
--cc=yu.c.chen@intel.com \
--cc=zangchunxin@lixiang.com \
--cc=zhouchunhua@lixiang.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®