From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] HZ: 300Hz support
Date: Wed, 08 Nov 2006 22:01:19 +0100 [thread overview]
Message-ID: <4552459F.7000709@gmail.com> (raw)
In-Reply-To: <1163018557.23956.92.camel@localhost.localdomain>
Alan Cox wrote:
> 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.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
>
> diff -u --new-file --recursive --exclude-from /usr/src/exclude
> linux.vanilla-2.6.19-rc4-mm1/kernel/Kconfig.hz
> linux-2.6.19-rc4-mm1/kernel/Kconfig.hz
> --- linux.vanilla-2.6.19-rc4-mm1/kernel/Kconfig.hz 2006-10-31
> 15:40:54.000000000 +0000
> +++ linux-2.6.19-rc4-mm1/kernel/Kconfig.hz 2006-11-08 17:06:38.000000000
> +0000
> @@ -7,7 +7,7 @@
> default HZ_250
> help
> Allows the configuration of the timer frequency. It is customary
> - to have the timer interrupt run at 1000 HZ but 100 HZ may be more
> + to have the timer interrupt run at 1000 Hz but 100 Hz may be more
> beneficial for servers and NUMA systems that do not need to have
> a fast response for user interaction and that may experience bus
> contention and cacheline bounces as a result of timer interrupts.
> @@ -19,21 +19,30 @@
> config HZ_100
> bool "100 HZ"
[...]
> config HZ_250
> bool "250 HZ"
[...]
> + config HZ_300
> + bool "300 HZ"
[...]
> config HZ_1000
> bool "1000 HZ"
Shouldn't be these also changed (I mean those in quotes)?
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2006-11-08 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 20:42 [PATCH] HZ: 300Hz support Alan Cox
2006-11-08 20:48 ` Arjan van de Ven
2006-11-08 21:12 ` Alan Cox
2006-11-08 21:01 ` Jiri Slaby [this message]
2006-11-08 22:39 ` Willy Tarreau
2006-11-10 8:35 ` Andi Kleen
2006-11-10 12:10 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4552459F.7000709@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.