From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Chen Yu <yu.c.chen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Barry Song <21cnbao@gmail.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Len Brown <len.brown@intel.com>, Ben Segall <bsegall@google.com>,
Aubrey Li <aubrey.li@intel.com>,
Abel Wu <wuyun.abel@bytedance.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Tim Chen <tim.c.chen@intel.com>,
linux-kernel@vger.kernel.org,
Yicong Yang <yangyicong@hisilicon.com>,
Mohini Narkhede <mohini.narkhede@intel.com>
Subject: Re: [PATCH v4] sched/fair: Introduce SIS_UTIL to search idle CPU based on sum of util_avg
Date: Fri, 24 Jun 2022 09:34:49 +0530 [thread overview]
Message-ID: <4027cf04-d39e-d8fd-b3af-c1873757bb39@amd.com> (raw)
In-Reply-To: <20220624020723.GA11803@chenyu5-mobl1>
Hello Chenyu,
On 6/24/2022 7:37 AM, Chen Yu wrote:
>
> [..snip..]>
>> With v4 on the current tip, I don't see any need for
>> a special case for systems with smaller LLCs with
>> SIS_PROP disabled and SIS_UITL enable. Even SIS Efficiency
>> seems to be better with SIS_UTIL for hackbench.
>>
>> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
> Thanks again. Would you mind if I add this test report link into next patch
> version?
Sure.
I'm assuming the next version will disables SIS_PROP and only
keep SIS_UTIL enabled which is the same configuration we ran
during this round of testing. The results should stay the same :)
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2022-06-24 4:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 16:34 [PATCH v4] sched/fair: Introduce SIS_UTIL to search idle CPU based on sum of util_avg Chen Yu
2022-06-13 7:40 ` Yicong Yang
2022-06-13 8:06 ` Chen Yu
2022-06-13 8:54 ` Mel Gorman
2022-06-13 9:08 ` Chen Yu
2022-06-22 6:36 ` K Prateek Nayak
2022-06-24 2:07 ` Chen Yu
2022-06-24 4:04 ` K Prateek Nayak [this message]
2022-06-24 12:27 ` Chen Yu
2022-06-24 7:29 ` Peter Zijlstra
2022-06-24 12:18 ` Chen Yu
2022-06-28 7:16 ` [tip: sched/core] " tip-bot2 for Chen Yu
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=4027cf04-d39e-d8fd-b3af-c1873757bb39@amd.com \
--to=kprateek.nayak@amd.com \
--cc=21cnbao@gmail.com \
--cc=aubrey.li@intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mohini.narkhede@intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tim.c.chen@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=wuyun.abel@bytedance.com \
--cc=yangyicong@hisilicon.com \
--cc=yu.c.chen@intel.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