From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: topology: Tell the scheduler about the relative power of cores
Date: Tue, 20 May 2014 18:37:27 +0100 [thread overview]
Message-ID: <20140520173727.GD28293@arm.com> (raw)
In-Reply-To: <1400545421-28067-1-git-send-email-broonie@kernel.org>
On Tue, May 20, 2014 at 01:23:40AM +0100, Mark Brown wrote:
> In heterogeneous systems like big.LITTLE systems the scheduler will be
> able to make better use of the available cores if we provide power numbers
> to it indicating their relative performance. Do this by parsing the CPU
> nodes in the DT.
Last time we discussed these two patches, my understanding was that the
mainline scheduler doesn't behave any better on big.LITTLE with this
additional information, unless you also have additional out of tree b.L
MP patches. Vincent is also cleaning up some of the cpu_power usage in
the scheduler.
So unless there are clear benefits in providing such information to the
mainline scheduler, I don't plan to merge them for the time being (I'm
also not convinced of the numbers in the second patch, they need some
benchmarking on real hardware).
--
Catalin
next prev parent reply other threads:[~2014-05-20 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 0:23 [PATCH 1/2] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2014-05-20 0:23 ` [PATCH 2/2] arm64: topology: Provide relative power numbers for cores Mark Brown
2014-05-20 17:37 ` Catalin Marinas [this message]
2014-05-20 18:45 ` [PATCH 1/2] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2014-05-20 21:31 ` Nicolas Pitre
2014-05-22 10:35 ` Catalin Marinas
2014-05-22 15:18 ` Mark Brown
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=20140520173727.GD28293@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).