public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 6/6] ARM: sched: clear SD_SHARE_POWERLINE
Date: Fri, 2 Nov 2012 16:30:21 +0530	[thread overview]
Message-ID: <5093A7C5.9080605@ti.com> (raw)
In-Reply-To: <CAKfTPtAZjLpwHYgj8JXku4sU0mPPf34MKkWp0=qiX5u-T0JVOA@mail.gmail.com>

On Monday 29 October 2012 06:58 PM, Vincent Guittot wrote:
> On 24 October 2012 17:21, Santosh Shilimkar <santosh.shilimkar@ti•com> wrote:
>> On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
>>>
>>> The ARM platforms take advantage of packing small tasks on few cores.
>>> This is true even when the cores of a cluster can't be powergated
>>> independently.
>>>
>>>
>>> Signed-off-by: Vincent Guittot <vincent.guittot@linaro•org>
>>> ---
>>>    arch/arm/kernel/topology.c |    5 +++++
>>>    1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/kernel/topology.c b/arch/arm/kernel/topology.c
>>> index 26c12c6..00511d0 100644
>>> --- a/arch/arm/kernel/topology.c
>>> +++ b/arch/arm/kernel/topology.c
>>> @@ -226,6 +226,11 @@ static inline void update_cpu_power(unsigned int
>>> cpuid, unsigned int mpidr) {}
>>>     */
>>>    struct cputopo_arm cpu_topology[NR_CPUS];
>>>
>>> +int arch_sd_share_power_line(void)
>>> +{
>>> +       return 0*SD_SHARE_POWERLINE;
>>> +}
>>
>>
>> Making this selection of policy based on sched domain will better. Just
>> gives the flexibility to choose a separate scheme for big and little
>> systems which will be very convenient.
>
> I agree that it would be more flexible to be able to set it for each level
>
Will you be addressing that in next version then ?

Regards
santosh

  reply	other threads:[~2012-11-02 11:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07  7:43 [RFC 0/6] sched: packing small tasks Vincent Guittot
2012-10-07  7:43 ` [RFC 1/6] Revert "sched: introduce temporary FAIR_GROUP_SCHED dependency for load-tracking" Vincent Guittot
2012-10-07  7:43 ` [RFC 2/6] sched: add a new SD SHARE_POWERLINE flag for sched_domain Vincent Guittot
2012-10-24 15:17   ` Santosh Shilimkar
2012-10-29  9:40     ` Vincent Guittot
2012-10-29  9:50       ` Vincent Guittot
2012-11-02 10:27         ` Santosh Shilimkar
2012-10-07  7:43 ` [RFC 3/6] sched: pack small tasks Vincent Guittot
2012-10-24 15:20   ` Santosh Shilimkar
2012-10-29 13:12     ` Vincent Guittot
2012-11-02 10:53       ` Santosh Shilimkar
2012-11-09 16:46         ` Morten Rasmussen
2012-11-12 13:13           ` Vincent Guittot
2012-11-12  9:30         ` Vincent Guittot
2012-11-09 17:13   ` Morten Rasmussen
2012-11-12 13:51     ` Vincent Guittot
2012-11-20 14:28       ` Morten Rasmussen
2012-11-20 16:59         ` Vincent Guittot
2012-10-07  7:43 ` [RFC 4/6] sched: secure access to other CPU statistics Vincent Guittot
2012-10-24 15:21   ` Santosh Shilimkar
2012-10-29 13:18     ` Vincent Guittot
2012-10-07  7:43 ` [RFC 5/6] sched: pack the idle load balance Vincent Guittot
2012-10-24 15:21   ` Santosh Shilimkar
2012-10-29 13:27     ` Vincent Guittot
2012-11-02 10:59       ` Santosh Shilimkar
2012-10-07  7:43 ` [RFC 6/6] ARM: sched: clear SD_SHARE_POWERLINE Vincent Guittot
2012-10-24 15:21   ` Santosh Shilimkar
2012-10-29 13:28     ` Vincent Guittot
2012-11-02 11:00       ` Santosh Shilimkar [this message]
2012-11-12  8:23         ` Vincent Guittot

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=5093A7C5.9080605@ti.com \
    --to=santosh.shilimkar@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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