On 05/17/2017 12:52 AM, Vincent Guittot wrote:
On 12 May 2017 at 22:19, Rohit Jain wrote:
On 05/12/2017 12:46 PM, Peter Zijlstra wrote:
On Fri, May 12, 2017 at 11:04:26AM -0700, Rohit Jain wrote:
The patch avoids CPUs which might be considered interrupt-heavy when
trying to schedule threads (o
On 12 May 2017 at 22:19, Rohit Jain wrote:
> On 05/12/2017 12:46 PM, Peter Zijlstra wrote:
>>
>> On Fri, May 12, 2017 at 11:04:26AM -0700, Rohit Jain wrote:
>>>
>>> The patch avoids CPUs which might be considered interrupt-heavy when
>>> trying to schedule threads (on the push side) in the system.
On 05/12/2017 12:46 PM, Peter Zijlstra wrote:
On Fri, May 12, 2017 at 11:04:26AM -0700, Rohit Jain wrote:
The patch avoids CPUs which might be considered interrupt-heavy when
trying to schedule threads (on the push side) in the system. Interrupt
Awareness has only been added into the fair schedu
On Fri, May 12, 2017 at 11:04:26AM -0700, Rohit Jain wrote:
> The patch avoids CPUs which might be considered interrupt-heavy when
> trying to schedule threads (on the push side) in the system. Interrupt
> Awareness has only been added into the fair scheduling class.
>
> It does so by, using the f
The patch avoids CPUs which might be considered interrupt-heavy when
trying to schedule threads (on the push side) in the system. Interrupt
Awareness has only been added into the fair scheduling class.
It does so by, using the following algorithm:
--
5 matches
Mail list logo