From: Borislav Petkov <bp@alien8.de>
To: Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>,
Robin Randhawa <Robin.Randhawa@ARM.com>,
Steve Bannister <Steve.Bannister@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
Date: Tue, 5 Feb 2013 12:39:50 +0100 [thread overview]
Message-ID: <20130205113950.GG4827@pd.tnic> (raw)
In-Reply-To: <80D6EFE2711DED4189C7C8F0430BFEA86D23D6A80E@BUNGLE.Emea.Arm.com>
On Tue, Feb 05, 2013 at 11:29:04AM +0000, Charles Garcia-Tobin wrote:
> Actually shooting myself in the foot here, Krait is not such a great
> example because although you can use difference between frequencies
> you are less likely to use different tunables (not inconceivable
> but unlikely). The best examples systems are multi cluster and
> hereterogeneous systems, like the recently announced Samsung Exynos 5
> octa http://en.wikipedia.org/wiki/Exynos_(system_on_chip). We will see
> more systems like this appearing, sporting low power cores combined
> with high performance ones, all running at the same time. I appreciate
> this is all very new, but more will come, and the requirement to have
> different tunables per cluster is very real. In ARM on our own multi
> cluster test chip, using an experimental version of this approach, we
> have seen good improvements in power consumption without compromising
> performance.
Ok, thanks for giving this insight, this is useful.
Question: do you need the granularity of that control to be per cpu
(with that I mean what linux understands under "cpu," i.e. logical or
physical core) or does one governor suffice per a set of cores, or as
you call it, a cluster?
> (Apologies ahead for any bit my mail server appends, not much I can do
> about it)
Yeah, my condolences :-)
> -- IMPORTANT NOTICE: The contents of this email and any attachments
> are confidential and may also be privileged. If you are not the
> intended recipient, please notify the sender immediately and do not
> disclose the contents to any other person, use it for any purpose, or
> store or copy the information in any medium. Thank you.
Leaving it in, in case you haven't seen how it looks like :-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-02-05 11:39 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 11:38 [PATCH 0/4] CPUFreq: Implement per policy instances of governors Viresh Kumar
[not found] ` <cover.1359976493.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-04 11:38 ` [PATCH 1/4] cpufreq: Don't check cpu_online(policy->cpu) Viresh Kumar
2013-02-04 11:38 ` Viresh Kumar
2013-02-04 11:38 ` [PATCH 2/4] cpufreq: stats: Get rid of CPUFREQ_STATDEVICE_ATTR Viresh Kumar
2013-02-04 11:38 ` Viresh Kumar
2013-02-04 11:38 ` [PATCH 3/4] cpufreq: Add per policy governor-init/exit infrastructure Viresh Kumar
2013-02-04 11:38 ` Viresh Kumar
2013-02-04 11:38 ` [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors Viresh Kumar
2013-02-04 11:38 ` Viresh Kumar
2013-02-10 21:14 ` Francesco Lavra
2013-02-11 4:16 ` Viresh Kumar
2013-02-11 4:39 ` Viresh Kumar
2013-02-04 12:17 ` [PATCH 0/4] CPUFreq: " Rafael J. Wysocki
2013-02-04 12:17 ` Rafael J. Wysocki
2013-02-04 12:24 ` Viresh Kumar
2013-02-04 12:32 ` Borislav Petkov
2013-02-04 12:54 ` Viresh Kumar
2013-02-04 13:04 ` Borislav Petkov
2013-02-04 13:25 ` Viresh Kumar
2013-02-04 13:36 ` Borislav Petkov
2013-02-04 13:58 ` Viresh Kumar
2013-02-04 14:09 ` Borislav Petkov
2013-02-04 14:21 ` Viresh Kumar
2013-02-04 15:05 ` Borislav Petkov
2013-02-04 15:37 ` Viresh Kumar
2013-02-04 16:50 ` Borislav Petkov
2013-02-05 7:20 ` Viresh Kumar
2013-02-05 9:15 ` Borislav Petkov
[not found] ` <20130205091532.GA4827-fF5Pk5pvG8Y@public.gmane.org>
2013-02-05 9:47 ` Viresh Kumar
2013-02-05 9:47 ` Viresh Kumar
2013-02-05 10:27 ` Borislav Petkov
2013-02-05 10:43 ` Viresh Kumar
2013-02-05 11:04 ` Borislav Petkov
2013-02-05 11:12 ` Viresh Kumar
2013-02-05 11:19 ` Borislav Petkov
2013-02-05 11:26 ` Viresh Kumar
2013-02-05 11:32 ` Borislav Petkov
2013-02-05 12:24 ` Viresh Kumar
2013-02-05 13:22 ` Borislav Petkov
2013-02-05 13:55 ` Viresh Kumar
2013-02-05 9:36 ` Viresh Kumar
[not found] ` <CAKohpokejWugM+wP5xcqp0F9AggLxuEf9Ox5fDViMxJh1c+kEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 11:29 ` Charles Garcia-Tobin
2013-02-05 11:29 ` Charles Garcia-Tobin
2013-02-05 11:39 ` Borislav Petkov [this message]
2013-02-05 18:38 ` Charles Garcia-Tobin
2013-02-05 18:38 ` Charles Garcia-Tobin
2013-02-05 18:44 ` Borislav Petkov
2013-02-05 16:21 ` Viresh Kumar
2013-02-06 9:58 ` Viresh Kumar
2013-02-06 10:08 ` Amit Kucheria
2013-02-06 10:15 ` Viresh Kumar
2013-02-06 10:38 ` Rafael J. Wysocki
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=20130205113950.GG4827@pd.tnic \
--to=bp@alien8.de \
--cc=Charles.Garcia-Tobin@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Robin.Randhawa@ARM.com \
--cc=Steve.Bannister@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@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.