linux-kernel - Re: [PATCH] HZ: 300Hz support

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0611101309080.6068@yvahk01.tjqt.qr>
Date:	Fri, 10 Nov 2006 13:10:09 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Andi Kleen <ak@...e.de>
cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HZ: 300Hz support


>> Fix two things. Firstly the unit is "Hz" not "HZ". Secondly it is useful
>> to have 300Hz support when doing multimedia work. 250 is fine for us in
>> Europe but the US frame rate is 30fps (29.99 blah for pedants). 300
>> gives us a tick divisible by both 25 and 30, and for interlace work 50
>> and 60. It's also giving similar performance to 250Hz.
>> 
>> I'd argue we should remove 250 and add 300, but that might be excess
>> disruption for now.
>
>If we go down that path I would like to have 256.

Before we have tons of choosable HZ possibilities, I prefer 
http://lkml.org/lkml/2006/6/18/111 where the user can input his desired 
value.

>Why? There are still lots of systems with broken Interrupt 0 routing
>and usually on those the RTC works just fine. But unfortunately RTC
>can be only programmed to power of two frequencies. 256 would fit.


	-`J'
-- 
-
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/