| 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
| ||
|
Message-id: <op.wlkaootc6426ze@localhost.localdomain> Date: Tue, 02 Oct 2012 19:25:26 +0200 From: Uwaysi Bin Kareem <uwaysi.bin.kareem@...adoxuncreated.com> To: linux-kernel@...r.kernel.org Subject: Re: The 10ms averager in fair.c + granularity The 10 ms averager is not the only strange thing. Obviously there are some good things in this scheduler, since it performs quite well. But I am not criticising the good. But the documentation makes a distinction between desktop and server with the "resolution" parameter. I tried some values and "echo 4500000000 > sched_min_granularity_ns" which would be strongly tuned towards server, only reduced jitter in doom 3. Which means it is a good value for desktop. So that doesn`t seem to cohere with what is stated aswell. Anyway.. One needs to get really deep into the code to understand why it is so. So you know, I don know. I am going to take a look at it, and there probably won`t be any patch anytime soon. Peace Be With You. -- 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/
Powered by blists - more mailing lists