public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Bärwolf" <stephan.baerwolf@tu-ilmenau.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 00/10] scheduler-ticker > 1000Hz, nitromethane for linux ;-)
Date: Mon, 27 Feb 2012 13:53:26 +0100	[thread overview]
Message-ID: <4F4B7CC6.1030307@tu-ilmenau.de> (raw)

Hi all,

this is a not fully serious (this is why I only post it here without sendig it
directly via mail) patchset for:

        * tune the scheduler at configuration point
        * increase the ticker-frequency way above 1000Hz
        * tune the ticker-freq. from userspace during runtime

Of course this increases your systems overhead, but it enables you to have
more timer-triggered contexswitches per second and so (?)higher(?) interactivity.
(Of course after tuning some scheduler-parameters, min_gran, wakeup_gran ...)

An interesting feature might be the userspace controlling of the tickerfreq, too.
(Without disturbing HZ-dependend kernelcode, of course.)

I don't have very high hopes for an mainline integration ;-) but perhaps
there are people, who want to play with such stuff.
The Code is more or less an excerise and perhaps some reviewing would
be nice - so please contact me.
If (in the very unlikely case) there is enough interest in it, I can cleanup
the code and start maintaining it...

* The patch is diffed against 3.2.7
* The whole patchset is also downloadable as an bzipped archive at:
  http://www.matrixstorm.com/software/linux/nitromethane/linux-3.2.7-patches.tar.bz2

So now, please blame me "we don't need such s*it, it causes only overhead"... ;-)

regards Stephan

pub   4096R/FB9B12DB 2011-10-14 Stephan Bärwolf <stephan.baerwolf@tu-ilmenau.de>
 Primary key fingerprint: 2252 B41E 12DF 41AD 476F  7F36 084A 0911 FB9B 12DB



Stephan Baerwolf (10):
  menuconfig: implement new submenu for extended scheduler-options
  sched: implement the new menuconfig controlling of sched_tunables
  menuconfig: extend nitro-menu by responsiveness nitro options
  sched: implement the controlling of responsiveness-nitro-options
  menuconfig: extend nitro-menu by HZ-frequency Nitro
  hrtimer: implement the controlling of nitro-hzboost
  menuconfig: extend nitro-menu by priority-nitro
  sched: implement the controlling of priority-nitro
  menuconfig: extend nitro-menu by userspace-multiplier
  hrtimer/sysctl: implement the controlling of userspace multiplier

 arch/x86/Kconfig            |    4 +-
 include/linux/sched.h       |    8 ++
 kernel/Kconfig.hz           |    3 -
 kernel/Kconfig.sched        |  202 +++++++++++++++++++++++++++++++++++++++++++
 kernel/sched.c              |    9 ++
 kernel/sched_fair.c         |   58 +++++++++++--
 kernel/sysctl.c             |   16 ++++
 kernel/time/tick-common.c   |   33 +++++++
 kernel/time/tick-internal.h |   20 ++++
 kernel/time/tick-sched.c    |   51 +++++++++++
 10 files changed, 390 insertions(+), 14 deletions(-)
 create mode 100644 kernel/Kconfig.sched

-- 
1.7.3.4

             reply	other threads:[~2012-02-27 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 12:53 Stephan Bärwolf [this message]
2012-02-28 10:53 ` [PATCH] nitro: make multiplier scaleable, change "nitro_hzmultiplicator" into "nitro_hz_permille" Stephan Bärwolf

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=4F4B7CC6.1030307@tu-ilmenau.de \
    --to=stephan.baerwolf@tu-ilmenau.de \
    --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