linux-kernel - Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <82e4877d0805051440o273b6a6dge7f0af310c266fb7@mail.gmail.com>
Date:	Mon, 5 May 2008 17:40:49 -0400
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Arjan van de Ven" <arjan@...radead.org>,
	"Sam Ravnborg" <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"akpm@...l.org" <akpm@...ux-foundation.org>,
	"Peter Zijlstra" <peterz@...radead.org>,
	"Dave Jones" <davej@...hat.com>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED

On Mon, May 5, 2008 at 5:05 PM, Ingo Molnar <mingo@...e.hu> wrote:
>

>  This is now believed to be fixed in sched-devel.git, via the "single
>  runqueue" and deadline-scheduling patches from Peter that flattens the
>  hierarchy of the group scheduler.
>
>  Another latency source was the skew of sched_clock() running too slow -
>  that way if the clock runs at 10% of its intended speed the scheduler
>  will turn a 40msec intended latency target into a 400 msec latency
>  target!
>
>  This bug too is now believed to be fixed via Peter's new sched_clock
>  code in sched-devel.git.

Ok, but the latency problems are not fixed with sched-devel as of
today. I still get unusable audio if I enable GROUP_SCHED stuff on
sched-devel and run make -j8 .

Parag
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/