On Wed, Mar 28, 2018 at 10:41 PM, Doug Smythies wrote:
> On 2018.03.28 08:15 Thomas Ilsche wrote:
>> On 2018-03-28 12:56, Rafael J. Wysocki wrote:
>>> On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki
>>> wrote:
On Wed, Mar 28, 2018 at 10:38 AM,
On Wed, Mar 28, 2018 at 10:41 PM, Doug Smythies wrote:
> On 2018.03.28 08:15 Thomas Ilsche wrote:
>> On 2018-03-28 12:56, Rafael J. Wysocki wrote:
>>> On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki
>>> wrote:
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
> On
On 2018.03.28 08:15 Thomas Ilsche wrote:
> On 2018-03-28 12:56, Rafael J. Wysocki wrote:
>> On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki
>> wrote:
>>> On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
>>> wrote:
On 2018-03-28 10:13,
On 2018.03.28 08:15 Thomas Ilsche wrote:
> On 2018-03-28 12:56, Rafael J. Wysocki wrote:
>> On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki
>> wrote:
>>> On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
>>> wrote:
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>
>>
>> [cut]
>>
>>>
On 2018-03-28 12:56, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
[cut]
So I do
$ for cpu in 0 1
On 2018-03-28 12:56, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
[cut]
So I do
$ for cpu in 0 1 2 3; do taskset -c $cpu sh -c 'while true; do
On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki wrote:
> On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
> wrote:
>> On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>>>
[cut]
>
> So I do
>
> $ for cpu in 0 1 2 3; do taskset -c $cpu sh -c 'while
On Wed, Mar 28, 2018 at 12:37 PM, Rafael J. Wysocki wrote:
> On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
> wrote:
>> On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>>>
[cut]
>
> So I do
>
> $ for cpu in 0 1 2 3; do taskset -c $cpu sh -c 'while true; do usleep
> 500; done' & done
>
> which
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
> On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>>
>> On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki
>> wrote:
>>>
>>> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
> On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>>
>> On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki
>> wrote:
>>>
>>> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
On 2018-03-20 16:45, Rafael J. Wysocki
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
On 2018-03-20 16:45, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
In
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
On 2018-03-20 16:45, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
In order to address the issue with short idle
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
>> On 2018-03-20 16:45, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > In order to address the issue with
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
>> On 2018-03-20 16:45, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > In order to address the issue with short idle duration predictions
>> > by the
On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
> On 2018-03-20 16:45, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > In order to address the issue with short idle duration predictions
> > by the idle governor after the tick has been
On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
> On 2018-03-20 16:45, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > In order to address the issue with short idle duration predictions
> > by the idle governor after the tick has been stopped, reorder the
> > code
On 2018-03-20 16:45, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
In order to address the issue with short idle duration predictions
by the idle governor after the tick has been stopped, reorder the
code in cpuidle_idle_call() so that the governor idle state
On 2018-03-20 16:45, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
In order to address the issue with short idle duration predictions
by the idle governor after the tick has been stopped, reorder the
code in cpuidle_idle_call() so that the governor idle state selection
runs before
From: Rafael J. Wysocki
In order to address the issue with short idle duration predictions
by the idle governor after the tick has been stopped, reorder the
code in cpuidle_idle_call() so that the governor idle state selection
runs before tick_nohz_idle_go_idle() and
From: Rafael J. Wysocki
In order to address the issue with short idle duration predictions
by the idle governor after the tick has been stopped, reorder the
code in cpuidle_idle_call() so that the governor idle state selection
runs before tick_nohz_idle_go_idle() and use the "nohz" hint returned
20 matches
Mail list logo