mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: "Dr. Martin Rogge" <marogge@onlinehome.de>
Cc: Gene Heskett <gene.heskett@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: scheduling policy    was: Re: 2.6.37 considered stable?
Date: Sat, 05 Feb 2011 07:32:09 +0100	[thread overview]
Message-ID: <1296887529.27896.14.camel@marge.simson.net> (raw)
In-Reply-To: <201102042123.28734.marogge@onlinehome.de>

On Fri, 2011-02-04 at 21:23 +0100, Dr. Martin Rogge wrote:
> Gene Heskett wrote:
> > Chuckle.  I've been running 2.6.37 here, with all of that new group
> > scheduling stuff enabled, the desktop feels great and my only fuss is that
> > kaffiene, when watching digital tv on my pcHD-3000 card, is NOT getting
> > enough time so both the audio and the video have little 20 millisecond
> > holes chopped in them at sub-second intervals.  Not the most pleasant
> > thing
> > to watch.  I would appreciate any suggestions on how to get such an
> > application a higher priority.
> > 
> 
> Gene, have you tried schedtool to set the scheduling policy of the process to 
> SCHED_FIFO or even SCHED_ISO?

/*
 * Scheduling policies
 */
#define SCHED_NORMAL            0
#define SCHED_FIFO              1
#define SCHED_RR                2
#define SCHED_BATCH             3
/* SCHED_ISO: reserved but not implemented yet */
#define SCHED_IDLE 

> Before anyone asks, yes, relying on schedtool puts a little reponsibility on 
> user space, but it is my firm believe that (a) you can't auto-everything and 
> (b) the onus should be on the distro not the user.

You only want to run apps RT if they really really need it though.  In
many cases, running an app RT will reduce performance, and may well
increase latencies.  (deterministic != quick like a bunny;)

	-Mike


  reply	other threads:[~2011-02-05  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 20:23 Dr. Martin Rogge
2011-02-05  6:32 ` Mike Galbraith [this message]
2011-02-05 12:27   ` Dr. Martin Rogge

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=1296887529.27896.14.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marogge@onlinehome.de \
    /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

all inboxes | Powered by JetHome®