From: Peter Zijlstra <peterz@infradead.org>
To: Subhra Mazumdar <subhra.mazumdar@oracle.com>
Cc: Steven Sistare <steven.sistare@oracle.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
dhaval.giani@oracle.com
Subject: Re: [RESEND RFC PATCH V3] sched: Improve scalability of select_idle_sibling using SMT balance
Date: Tue, 6 Feb 2018 10:12:39 +0100 [thread overview]
Message-ID: <20180206091239.GA2269@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <930364e4-bbfe-8c8f-d095-0dd4256a5104@oracle.com>
On Mon, Feb 05, 2018 at 02:09:11PM -0800, Subhra Mazumdar wrote:
> The pseudo random is also used for choosing a random core to compare with,
> how will transposing achieve that?
Not entirely sure what your point is. Current code doesn't compare to
just _one_ other core, and I don't think we'd ever want to do that.
So currently select_idle_core() will, if there is an idle core, iterate
the whole thing trying to find it. If it fails, it clears the
'have_idle_core' state.
select_idle_cpu, which we'll fall back to, will limit the scanning based
on the average idle time.
The crucial point however, is that concurrent wakeups will not, on
average, do the same iteration because of the target offset.
next prev parent reply other threads:[~2018-02-06 9:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 23:31 [RESEND RFC PATCH V3] sched: Improve scalability of select_idle_sibling using SMT balance subhra mazumdar
2018-02-01 12:33 ` Peter Zijlstra
2018-02-01 13:33 ` Peter Zijlstra
2018-02-02 16:53 ` Steven Sistare
2018-02-02 17:17 ` Peter Zijlstra
2018-02-02 17:36 ` Steven Sistare
2018-02-02 19:58 ` Peter Zijlstra
2018-02-02 20:51 ` Steven Sistare
2018-02-02 17:37 ` Subhra Mazumdar
2018-02-05 12:19 ` Peter Zijlstra
2018-02-05 22:09 ` Subhra Mazumdar
2018-02-06 9:12 ` Peter Zijlstra [this message]
2018-02-07 0:30 ` Subhra Mazumdar
2018-02-07 8:42 ` Peter Zijlstra
2018-02-07 23:10 ` Subhra Mazumdar
2018-02-02 17:21 ` Peter Zijlstra
2018-02-02 17:39 ` Steven Sistare
2018-02-02 18:34 ` Steven Sistare
2018-02-02 20:04 ` Peter Zijlstra
2018-02-02 21:17 ` Steven Sistare
2018-02-03 3:47 ` Mike Galbraith
2018-02-02 19:59 ` Peter Zijlstra
2018-02-02 21:06 ` Steven Sistare
2018-02-05 12:48 ` Peter Zijlstra
2018-02-05 13:54 ` Mike Galbraith
2018-02-05 17:03 ` Peter Zijlstra
2018-02-05 22:32 ` Subhra Mazumdar
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=20180206091239.GA2269@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dhaval.giani@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=steven.sistare@oracle.com \
--cc=subhra.mazumdar@oracle.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