From: Peter Zijlstra <peterz@infradead.org>
To: Subhra Mazumdar <subhra.mazumdar@oracle.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [RFC PATCH] sched: select_idle_core should select least utilized core
Date: Thu, 8 Jun 2017 21:59:00 +0200 [thread overview]
Message-ID: <20170608195900.GA8337@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1496949992-629076-1-git-send-email-subhra.mazumdar@oracle.com>
On Thu, Jun 08, 2017 at 03:26:32PM -0400, Subhra Mazumdar wrote:
> Current select_idle_core tries to find a fully idle core and if it fails
> select_idle_cpu next returns any idle cpu in the llc domain. This is not optimal
> for architectures with many (more than 2) hyperthreads in a core. This patch
> changes select_idle_core to find the core with least number of busy
> hyperthreads and return an idle cpu in that core.
Yeah, I think not. That makes select_idle_siblings _vastly_ more
expensive.
next prev parent reply other threads:[~2017-06-08 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 19:26 [RFC PATCH] sched: select_idle_core should select least utilized core Subhra Mazumdar
2017-06-08 19:59 ` Peter Zijlstra [this message]
2017-06-08 22:06 ` subhra mazumdar
2017-06-09 7:53 ` Peter Zijlstra
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=20170608195900.GA8337@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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