From: Chen Yu <yu.c.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
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 20:18:31 +0800 [thread overview]
Message-ID: <20220624121831.GA5570@chenyu5-mobl1> (raw)
In-Reply-To: <YrVn9t2kLHB21uG1@hirez.programming.kicks-ass.net>
On Fri, Jun 24, 2022 at 09:29:58AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 22, 2022 at 12:06:55PM +0530, K Prateek Nayak wrote:
> > Hello Chenyu,
> >
> > I'm sorry for the delay. The testing took a while but below are
> > the results from testing on our system.
> >
> > tl;dr
> >
> > o We ran all the tests with with SIS_PROP disabled.
> > o tbench reaches close to saturation early with 256 clients.
> > o schbench shows improvements for low worker counts.
> > o All other benchmark results seem comparable to tip.
> > We don't see any serious regressions with v4.
> >
> > > @@ -61,6 +61,7 @@ SCHED_FEAT(TTWU_QUEUE, true)
> > > * When doing wakeups, attempt to limit superfluous scans of the LLC domain.
> > > */
> > > SCHED_FEAT(SIS_PROP, true)
> >
> > SIS_PROP was disabled in our testing as follows:
> >
> > --
> > -SCHED_FEAT(SIS_PROP, true)
> > +SCHED_FEAT(SIS_PROP, false)
>
> So how about I make this change.
>
> > 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>
>
> And apply this thing, lets see how it fares..
OK, thanks, Peter.
Best,
Chenyu
next prev parent reply other threads:[~2022-06-24 12:18 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
2022-06-24 12:27 ` Chen Yu
2022-06-24 7:29 ` Peter Zijlstra
2022-06-24 12:18 ` Chen Yu [this message]
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=20220624121831.GA5570@chenyu5-mobl1 \
--to=yu.c.chen@intel.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=kprateek.nayak@amd.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 \
/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