From: Valdis.Kletnieks@vt.edu
To: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Psychovisually-optimized HZ setting (2.6.33.3)
Date: Tue, 27 Apr 2010 17:50:03 -0400 [thread overview]
Message-ID: <29999.1272405003@localhost> (raw)
In-Reply-To: Your message of "Tue, 27 Apr 2010 21:03:11 +0200." <op.vbt4jlyn6426ze@millennium.getinternet.no>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Tue, 27 Apr 2010 21:03:11 +0200, Uwaysi Bin Kareem said:
> http://www.paradoxuncreated.com/articles/Millennium/Millennium.html
> + config HZ_3956
> + bool "3956 HZ"
> + help
> + 3956 Hz is nearly the highest timer interrupt rate supported in the kernel.
> + Graphics workstations, and OpenGL applications may benefit from this,
> + since it gives the lowest framerate-jitter. The exact value 3956 is
> + psychovisually-optimized, meaning that it aims for a level of jitter,
Even after reading your link, it's unclear why 3956 and not 4000. All your link
said was "A granularity below 0.5 milliseconds, seems to suit the human
senses." - anything over 2000 meets that requirement. Also, if your screen
refresh is sitting at 72hz or a bit under 14ms per refresh, any jitter under
that won't really matter much - it doesn't matter if your next frame is
ready 5ms early or 5.5ms early, you *still* have to wait for the next vertical
blanking interval or suffer tearing.
There's also the case of programs where HZ=300 would *make* the time budget,
but the added 3,356 timer interrupts and associated overhead would cause a
missed screen refresh.
I think you need more technical justification of why 3956 is better than 1000.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-04-27 21:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2030-04-14 9:05 [PATCH V3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side Zhang, Yanmin
2010-04-14 9:20 ` Avi Kivity
2010-04-14 9:43 ` Sheng Yang
2010-04-14 9:57 ` Avi Kivity
2010-04-14 10:14 ` Sheng Yang
2010-04-14 10:19 ` Avi Kivity
2010-04-14 10:27 ` Sheng Yang
2010-04-14 10:33 ` Avi Kivity
2010-04-14 10:36 ` Sheng Yang
2010-04-14 10:43 ` Ingo Molnar
2010-04-14 11:17 ` Avi Kivity
2030-04-15 1:04 ` Zhang, Yanmin
2010-04-15 8:05 ` Avi Kivity
2030-04-15 8:57 ` Zhang, Yanmin
2010-04-15 9:04 ` oerg Roedel
2010-04-15 9:09 ` Avi Kivity
2010-04-15 9:44 ` oerg Roedel
2010-04-15 9:48 ` Avi Kivity
2010-04-15 10:40 ` Joerg Roedel
2010-04-15 10:44 ` Avi Kivity
2010-04-15 14:08 ` Sheng Yang
2010-04-17 18:12 ` Avi Kivity
2010-04-19 8:25 ` Avi Kivity
2010-04-20 3:32 ` Sheng Yang
2010-04-20 9:38 ` Avi Kivity
2010-04-27 19:03 ` [PATCH] Psychovisually-optimized HZ setting (2.6.33.3) Uwaysi Bin Kareem
2010-04-27 19:51 ` Randy Dunlap
2010-04-27 21:50 ` Valdis.Kletnieks [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-01 14:12 uwaysi.bin.kareem
2010-06-01 10:47 uwaysi.bin.kareem
2010-06-01 13:25 ` Valdis.Kletnieks
2010-05-29 11:54 uwaysi.bin.kareem
2010-06-01 6:21 ` Valdis.Kletnieks
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=29999.1272405003@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=uwaysi.bin.kareem@paradoxuncreated.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox