public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ove Karlsen <ove.karlsen@paradoxuncreated.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: One last tweak for perfection.
Date: Wed, 16 Jan 2013 15:02:55 +0100	[thread overview]
Message-ID: <50F6B30F.6010207@paradoxuncreated.com> (raw)
In-Reply-To: <50F6B254.2020801@paradoxuncreated.com>

What kernelthreads _needs_ to run? So I can put them on max pri renice, 
along with reniced X and app. And everything else on idle priority. So 
to make the app run at max efficiency, and not be starved by 
kernelthreads waiting. (Or any other consideration, for giving maximal 
cpu to app. Even small tweaks.)

To read my research so far, (and I have done much, about 2 years of 
tweakin´ on and off.) Please see 
http://paradoxuncreated.com/Blog/wordpress/?p=2268

Main points, no highres timer, 90hz timer, + a lot of smaller tweaks. 
This makes an amazing linux-desktop, for gaming, video and audio. The 
popular computer for everyman. Also boosts performance, for 
resource-constrained systems.

For more advanced hacking, one could also get in there, and make several 
HZ timers, extremely low ones, for the components who only require that, 
and 90hz for video-components, for instance (low video/frame jitter), 
and higher if anything should require that.

Also system-wide, software should be synced to hz, if required for 
lowest jitter, such as animations and videoplayers, and videoplayers 
automatically change refresh rate to a multiple of video framerate.

Peace Be With You.

  reply	other threads:[~2013-01-16 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 13:59 One last tweak for perfection Ove Karlsen
2013-01-16 14:02 ` Ove Karlsen [this message]
2013-01-16 14:25   ` Ove Karlsen
2013-01-16 14:27     ` Ove Karlsen
2013-01-16 14:28       ` Ove Karlsen
2013-01-16 14:36         ` Ove Karlsen

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=50F6B30F.6010207@paradoxuncreated.com \
    --to=ove.karlsen@paradoxuncreated.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox