On Fri, Jun 23, 2017 at 12:55:29PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> Since select_idle_sibling can place a task anywhere on a socket,
> comparing loads between individual CPU cores makes no real sense
> for deciding whether to do an affine wakeup across
On Fri, Jun 23, 2017 at 12:55:29PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> Since select_idle_sibling can place a task anywhere on a socket,
> comparing loads between individual CPU cores makes no real sense
> for deciding whether to do an affine wakeup across sockets, either.
>
>
From: Rik van Riel
Since select_idle_sibling can place a task anywhere on a socket,
comparing loads between individual CPU cores makes no real sense
for deciding whether to do an affine wakeup across sockets, either.
Instead, compare the load between the sockets in a similar
From: Rik van Riel
Since select_idle_sibling can place a task anywhere on a socket,
comparing loads between individual CPU cores makes no real sense
for deciding whether to do an affine wakeup across sockets, either.
Instead, compare the load between the sockets in a similar way the
load
4 matches
Mail list logo