From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH 1/2] ARM64: add cpu topology definition
Date: Mon, 29 Jul 2013 11:15:07 +0100 [thread overview]
Message-ID: <51F640AB.2050709@arm.com> (raw)
In-Reply-To: <CAKfTPtBpo41LJ3V8TB8YwudwqpURuA2u_Lvu4KYVK=qSs+gFuQ@mail.gmail.com>
On 29/07/13 10:46, Vincent Guittot wrote:
> On 27 July 2013 12:42, Hanjun Guo <hanjun.guo@linaro.org> wrote:
>> Power aware scheduling needs the cpu topology information to improve the
>> cpu scheduler decision making.
>
> It's not only power aware scheduling. The scheduler already uses
> topology and cache sharing when CONFIG_SCHED_MC and/or
> CONFIG_SCHED_SMT are enable. So you should also add these configs for
> arm64 so the scheduler can use it
>
Just for my knowledge, I thought power aware using SCHED_MC/SMT was
removed. I see commit 8e7fbcbc22c12414bcc9dfdd683637f58fb32759 "sched:
Remove stale power aware scheduling remnants and dysfunctional knobs"
I may be missing something here.
Regards,
Sudeep
next prev parent reply other threads:[~2013-07-29 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 10:42 [RFC][PATCH 1/2] ARM64: add cpu topology definition Hanjun Guo
2013-07-27 10:42 ` [RFC][PATCH 2/2] ARM64: introduce cluster id and make a difference between socket id Hanjun Guo
2013-07-29 9:38 ` Vincent Guittot
2013-07-30 7:46 ` Hanjun Guo
2013-07-29 9:46 ` [RFC][PATCH 1/2] ARM64: add cpu topology definition Vincent Guittot
2013-07-29 9:54 ` Will Deacon
2013-07-29 10:39 ` Vincent Guittot
2013-07-29 13:36 ` Dave Martin
2013-07-29 17:23 ` Lorenzo Pieralisi
2013-07-30 8:09 ` Hanjun Guo
2013-08-14 11:27 ` Catalin Marinas
2013-08-15 1:00 ` Hanjun Guo
2013-07-29 10:15 ` Sudeep KarkadaNagesha [this message]
2013-07-29 10:28 ` Vincent Guittot
2013-07-30 7:49 ` Hanjun Guo
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=51F640AB.2050709@arm.com \
--to=sudeep.karkadanagesha@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).