Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-06 Thread Daniel Lezcano
[ ... ] The following patch is a hot fix by returning to the initial behavior by removing the lock when getting the driver. >>> >>> The patch fixes the problem. Verified on a system with 1024 cpus. >>> Thanks. >>> Signed-off-by: Daniel Lezcano >>> >>> Reported-by: Russ Anderson

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-06 Thread Daniel Lezcano
[ ... ] The following patch is a hot fix by returning to the initial behavior by removing the lock when getting the driver. The patch fixes the problem. Verified on a system with 1024 cpus. Thanks. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reported-by: Russ Anderson

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-04 Thread Rafael J. Wysocki
On Friday, January 04, 2013 07:27:24 AM Daniel Lezcano wrote: > On 01/02/2013 10:13 PM, Russ Anderson wrote: > > On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: > >> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces > >> a lock in the cpuidle_get_cpu_driver function.

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-04 Thread Rafael J. Wysocki
On Friday, January 04, 2013 07:27:24 AM Daniel Lezcano wrote: On 01/02/2013 10:13 PM, Russ Anderson wrote: On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-03 Thread Daniel Lezcano
On 01/02/2013 10:13 PM, Russ Anderson wrote: > On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: >> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces >> a lock in the cpuidle_get_cpu_driver function. This function >> is used in the idle_call function. >> >> The problem

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-03 Thread Daniel Lezcano
On 01/02/2013 10:13 PM, Russ Anderson wrote: On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This function is used in the idle_call function. The problem is the

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-02 Thread Russ Anderson
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: > The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces > a lock in the cpuidle_get_cpu_driver function. This function > is used in the idle_call function. > > The problem is the contention with a large number of cpus

Re: [PATCH] cpuidle - fix lock contention in the idle path

2013-01-02 Thread Russ Anderson
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote: The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This function is used in the idle_call function. The problem is the contention with a large number of cpus because

Re: [PATCH] cpuidle - fix lock contention in the idle path

2012-12-31 Thread Russ Anderson
On Sat, Dec 29, 2012 at 11:03:03AM +0100, Daniel Lezcano wrote: > > Hi Russ, > > Is it possible you try this patch on your 2048 cpus ? Yes, I will try it later today. Thanks > Thanks > > -- Daniel > > On 12/26/2012 11:01 AM, Daniel Lezcano wrote: > > The commit

Re: [PATCH] cpuidle - fix lock contention in the idle path

2012-12-31 Thread Russ Anderson
On Sat, Dec 29, 2012 at 11:03:03AM +0100, Daniel Lezcano wrote: Hi Russ, Is it possible you try this patch on your 2048 cpus ? Yes, I will try it later today. Thanks Thanks -- Daniel On 12/26/2012 11:01 AM, Daniel Lezcano wrote: The commit

Re: [PATCH] cpuidle - fix lock contention in the idle path

2012-12-29 Thread Daniel Lezcano
Hi Russ, Is it possible you try this patch on your 2048 cpus ? Thanks -- Daniel On 12/26/2012 11:01 AM, Daniel Lezcano wrote: > The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces > a lock in the cpuidle_get_cpu_driver function. This function > is used in the idle_call function.

Re: [PATCH] cpuidle - fix lock contention in the idle path

2012-12-29 Thread Daniel Lezcano
Hi Russ, Is it possible you try this patch on your 2048 cpus ? Thanks -- Daniel On 12/26/2012 11:01 AM, Daniel Lezcano wrote: The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This function is used in the idle_call function.

[PATCH] cpuidle - fix lock contention in the idle path

2012-12-26 Thread Daniel Lezcano
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This function is used in the idle_call function. The problem is the contention with a large number of cpus because they try to access the idle routine at the same time. The lock could be

[PATCH] cpuidle - fix lock contention in the idle path

2012-12-26 Thread Daniel Lezcano
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces a lock in the cpuidle_get_cpu_driver function. This function is used in the idle_call function. The problem is the contention with a large number of cpus because they try to access the idle routine at the same time. The lock could be