Sorry for the delay, got side-tracked for a bit..
On Wed, Dec 14, 2016 at 12:15:25AM -0500, Alexandre-Xavier Labonté-Lamoureux
wrote:
> > Which of the 4 patches does this?
>
> I used all the 4 patches at the same time. Each patch fixes a
> different bug. Would you like me to try each of them in
> Which of the 4 patches does this?
I used all the 4 patches at the same time. Each patch fixes a
different bug. Would you like me to try each of them individually?
Were you already aware of each of these bugs?
> Also, what hypervisor are you using and what does the output of booting
> with "sche
On Sun, Dec 11, 2016 at 04:41:51PM -0500, Alexandre-Xavier Labonté-Lamoureux
wrote:
>
> Here are my results (using "time make -j32" on my VM that has 4 cores):
>
> Kernel 4.8.14
> real 26m56.151s
> user 79m52.472s
> sys 7m42.964s
>
> Same kernel, but patched:
> real 4m25.238s
> user 1
Hi,
There's a research paper[1] called "The Linux Scheduler: a Decade of
Wasted Cores". It shows how the Linux Kernel scheduler is broken and
they provided fixes[2] for some of the know issues that it has. The
changes are illustrated in a presentation[3] that was shown during a
talk.
I patched my
4 matches
Mail list logo