2012/12/22 Steven Rostedt :
> The idle_balance() code is called to do task load balancing just before
> going to idle. This makes sense as the CPU is about to sleep anyway.
> But currently it's called in the middle of the scheduler and in a place
> that must have interrupts disabled. That means,
2012/12/22 Steven Rostedt rost...@goodmis.org:
The idle_balance() code is called to do task load balancing just before
going to idle. This makes sense as the CPU is about to sleep anyway.
But currently it's called in the middle of the scheduler and in a place
that must have interrupts
---
So much for saying it was well tested. As my email box is separate from
the development boxes, I didn't copy the write set of patches over. This
patch was tested thoroughly on 40 core and 4 core, but not UP. The UP
had some bugs that were fixed (but not sent :-p)
Here's the correct patch with
The idle_balance() code is called to do task load balancing just before
going to idle. This makes sense as the CPU is about to sleep anyway.
But currently it's called in the middle of the scheduler and in a place
that must have interrupts disabled. That means, while the load balancing
is going on,
The idle_balance() code is called to do task load balancing just before
going to idle. This makes sense as the CPU is about to sleep anyway.
But currently it's called in the middle of the scheduler and in a place
that must have interrupts disabled. That means, while the load balancing
is going on,
---
So much for saying it was well tested. As my email box is separate from
the development boxes, I didn't copy the write set of patches over. This
patch was tested thoroughly on 40 core and 4 core, but not UP. The UP
had some bugs that were fixed (but not sent :-p)
Here's the correct patch with
6 matches
Mail list logo
