public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Alberto Gonzalez <info@gnebu.es>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about fair schedulers
Date: Sat, 23 Jun 2007 16:28:37 +0200	[thread overview]
Message-ID: <20070623162837.47f31bf8@localhost> (raw)
In-Reply-To: <200706231556.36430.info@gnebu.es>

On Sat, 23 Jun 2007 15:56:36 +0200
Alberto Gonzalez <info@gnebu.es> wrote:

> > And yes, programs/distributions should set good defaults for you... and
> > if they don't, just complain to them  :)  
> 
> I'm sure they'll do once a fair scheduler goes into mainline :)

Some already does... for example the current version of:
	http://www.exit1.org/dvdrip/

it sets transcode nice to "+19" by default  :)

> 
> I guess what I was missing from the beginning is that "fair" means that the 
> scheduler will be fair among tasks that have the same priority, but if a task 
> has a higher priority, it _will_ get more CPU. So we'll just have to mark 
> applications like video players, audio players or games with a high priority, 
> others like encoders or compilers with low priority, and leave the rest 
> (browsers, word processors, email readers, etc...) as normal priority. This 
> way a fair scheduler would be able to give each task right amount of CPU.

Yes. I think that the more important thing is to nice background tasks
(like encoders etc..), then games / video players can run without
problems even without renicing (usually normal programs don't eat much
CPU).

-- 
	Paolo Ornati
	Linux 2.6.22-rc5-g0864a4e2 on x86_64

      reply	other threads:[~2007-06-23 14:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 22:07 Question about fair schedulers Alberto Gonzalez
2007-06-23  0:55 ` Kyle Moffett
2007-06-23  7:46   ` Alberto Gonzalez
2007-06-23 16:35     ` Kyle Moffett
2007-06-23 17:28       ` Alberto Gonzalez
2007-06-24 20:57         ` Jesper Juhl
2007-06-24 19:36     ` David Schwartz
2007-06-26 12:19     ` Helge Hafting
2007-06-27 12:39   ` Alberto Gonzalez
2007-06-23  7:06 ` Paolo Ornati
2007-06-23  8:01   ` Alberto Gonzalez
2007-06-23  8:23     ` Willy Tarreau
2007-06-23  9:18       ` Alberto Gonzalez
2007-06-23  9:28         ` Russell Harmon
2007-06-23 10:30         ` Willy Tarreau
2007-06-23 10:45           ` Alberto Gonzalez
2007-06-23 10:50             ` Willy Tarreau
2007-06-23 11:00               ` Alberto Gonzalez
2007-06-23 11:05                 ` Tom Spink
2007-06-23 11:26                   ` Alberto Gonzalez
2007-06-23 11:51                     ` Willy Tarreau
2007-06-27 20:28                     ` Bill Davidsen
2007-06-23 13:26     ` Paolo Ornati
2007-06-23 13:56       ` Alberto Gonzalez
2007-06-23 14:28         ` Paolo Ornati [this message]

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=20070623162837.47f31bf8@localhost \
    --to=ornati@fastwebnet.it \
    --cc=info@gnebu.es \
    --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