From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Rik van Riel <riel@surriel.com>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <valentin.schneider@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>,
Gautham R Shenoy <ego@linux.vnet.ibm.com>,
Parth Shah <parth@linux.ibm.com>
Subject: Re: [PATCH] sched/fair: Prefer idle CPU to cache affinity
Date: Tue, 2 Mar 2021 13:09:46 +0530 [thread overview]
Message-ID: <20210302073946.GL2028034@linux.vnet.ibm.com> (raw)
In-Reply-To: <YD0h5I7qmDO2zlkE@hirez.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> [2021-03-01 18:18:28]:
> On Mon, Mar 01, 2021 at 10:36:01PM +0530, Srikar Dronamraju wrote:
> > * Peter Zijlstra <peterz@infradead.org> [2021-03-01 16:44:42]:
> >
> > > On Sat, Feb 27, 2021 at 02:56:07PM -0500, Rik van Riel wrote:
> > > > On Fri, 2021-02-26 at 22:10 +0530, Srikar Dronamraju wrote:
> > >
> > >
> > > > Maybe we could use "tnr_busy * 4 <
> > > > tllc_size * 3" or
> > > > something like that?
> > >
> > > How about:
> > >
> > > tnr_busy < tllc_size / topology_max_smt_threads()
> > >
> > > ?
> >
> > Isn't topology_max_smt_threads only for x86 as of today?
> > Or Am I missing out?
>
> Oh, could be, I didn't grep :/ We could have core code keep track of the
> smt count I suppose.
Could we use cpumask_weight(cpu_smt_mask(this_cpu)) instead?
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2021-03-02 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 16:40 [PATCH] sched/fair: Prefer idle CPU to cache affinity Srikar Dronamraju
2021-02-27 19:56 ` Rik van Riel
2021-03-01 13:37 ` Srikar Dronamraju
2021-03-01 15:44 ` Peter Zijlstra
2021-03-01 17:06 ` Srikar Dronamraju
2021-03-01 17:18 ` Peter Zijlstra
2021-03-02 7:39 ` Srikar Dronamraju [this message]
2021-03-02 9:10 ` Peter Zijlstra
2021-03-02 10:05 ` Srikar Dronamraju
2021-03-01 15:40 ` Peter Zijlstra
2021-03-01 17:08 ` Srikar Dronamraju
2021-03-02 9:53 ` Dietmar Eggemann
2021-03-02 10:04 ` Srikar Dronamraju
2021-03-08 13:52 ` Vincent Guittot
2021-03-10 5:52 ` Srikar Dronamraju
2021-03-10 15:37 ` 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=20210302073946.GL2028034@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mikey@neuling.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=parth@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.