On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
> Greetings,
>
> Minor change to the plan:
> * The current llct is *llct-20121006.0*
> * October 9: ll rebuild based on llct-20121006.0
> * October 16: ll rebuild based on llct-20121012., ll code freeze (no
>massive ll topics updates after th
On Thursday 04 of October 2012 14:58:33 Rajagopal Venkat wrote:
> Add devfreq suspend/resume apis for devfreq users. This patch
> supports suspend and resume of devfreq load monitoring, required
> for devices which can idle.
>
> Signed-off-by: Rajagopal Venkat
> Acked-by: MyungJoo Ham
Well, I w
On Tuesday 25 of September 2012 00:43:54 Daniel Lezcano wrote:
> With the tegra3 and the big.LITTLE [1] new architectures, several cpus
> with different characteristics (latencies and states) can co-exists on the
> system.
>
> The cpuidle framework has the limitation of handling only identical cpu
On Thursday 04 of October 2012 17:34:42 Peter De Schrijver wrote:
> > >>
> > >> eg.
> > >> cpu0: acpi_idle
> > >> cpu1: acpi_idle
> > >>
> > >
> > > Is this allowed? I thought sysfs files can output only 1 line of data?
> >
> > Ah yeah :)
> >
> > Does it make sense to put the following files:
>
On Tuesday 25 of September 2012 00:43:52 Daniel Lezcano wrote:
> The code checks if the driver is already set without taking the lock,
> but, right after, it takes the lock to assign the variable.
>
> If it is safe to check the variable without lock, then it is safe to
> assign it without lock. If
On 06/10/12 08:52, the mail apparently from Ricardo Salveti included:
On Fri, Oct 5, 2012 at 2:03 PM, Andrey Konovalov
wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you
The atomic update of runnable_avg_sum and runnable_avg_period are ensured
by their size and the toolchain. But we must ensure to not read an old value
for one field and a newly updated value for the other field. As we don't
want to lock other CPU while reading these fields, we read twice each field
This new flag SD SHARE_POWERLINE reflects the sharing of the power rail
between the members of a domain. As this is the current assumption of the
scheduler, the flag is added to all sched_domain
Signed-off-by: Vincent Guittot
---
arch/ia64/include/asm/topology.h |1 +
arch/tile/include/asm/t
Hi,
This patch-set takes advantage of the new statistics that are going to be
available in the kernel thanks to the per-entity load-tracking:
http://thread.gmane.org/gmane.linux.kernel/1348522. It packs the small tasks in
as few as possible CPU/Cluster/Core. The main goal of packing small tasks
This reverts commit f0494c69d387db9496b6f9aa71b3bc49f1dcf474.
Signed-off-by: Vincent Guittot
---
include/linux/sched.h |8 +---
kernel/sched/core.c |7 +--
kernel/sched/fair.c | 13 ++---
kernel/sched/sched.h |9 +
4 files changed, 5 insertions(+), 32 d
Look for an idle CPU close the pack buddy CPU whenever possible.
The goal is to prevent the wake up of a CPU which doesn't share the power
line of the pack CPU
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/kernel/
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
independantly.
Signed-off-by: Vincent Guittot
---
arch/arm/kernel/topology.c |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/kernel/topolog
During sched_domain creation, we define a pack buddy CPU if available.
On a system that share the powerline at all level, the buddy is set to -1
On a dual clusters / dual cores system which can powergate each core and
cluster independantly, the buddy configuration will be :
| CPU0 | CPU1 |
13 matches
Mail list logo
