From: Randy Dunlap <rdunlap@xenotime.net>
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 12:51:21 -0700 [thread overview]
Message-ID: <20100427125121.93963b8c.rdunlap@xenotime.net> (raw)
In-Reply-To: <op.vbt4jlyn6426ze@millennium.getinternet.no>
On Tue, 27 Apr 2010 21:03:11 +0200 Uwaysi Bin Kareem wrote:
> This is based on the research I did with optimizing my machine for
> graphics.
> I also wrote the following article:
> http://www.paradoxuncreated.com/articles/Millennium/Millennium.html
> It is a bit outdated now, but I will update it with current information.
> The value might iterate.
Hi,
What CPU architectures or platforms did you test this on?
Were any other kernel changes needed?
> Peace Be With You,
> Uwaysi Bin Kareem.
>
>
> --- Kconfig.hzorig 2010-04-27 13:33:10.302162524 +0200
> +++ Kconfig.hz 2010-04-27 20:39:54.736959816 +0200
> @@ -45,6 +45,18 @@
> 1000 Hz is the preferred choice for desktop systems and other
> systems requiring fast interactive responses to events.
>
> + 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,
drop first comma.
> + since it gives the lowest framerate-jitter. The exact value 3956 is
> + psychovisually-optimized, meaning that it aims for a level of jitter,
> + percieved to be natural, and therefore non-nosiy. It is tuned for a
perceived non-noisy.
> + profile of "where the human senses register the most information".
> +
> +
> +
> endchoice
>
> config HZ
> @@ -53,6 +65,7 @@
> default 250 if HZ_250
> default 300 if HZ_300
> default 1000 if HZ_1000
> + default 3956 if HZ_3956
>
> config SCHED_HRTICK
> def_bool HIGH_RES_TIMERS && (!SMP || USE_GENERIC_SMP_HELPERS)
>
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-04-27 19:51 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 [this message]
2010-04-27 21:50 ` Valdis.Kletnieks
-- 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=20100427125121.93963b8c.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--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;
as well as URLs for NNTP newsgroup(s).