public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Ash Milsted <thatistosayiseenem@gawab.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	ck list <ck@vds.kolivas.org>
Subject: Re: [ck] RSDL v0.30 cpu scheduler for mainline kernels
Date: Wed, 14 Mar 2007 02:46:26 +1100	[thread overview]
Message-ID: <200703140246.26522.kernel@kolivas.org> (raw)
In-Reply-To: <20070313153514.428dc3e1.thatistosayiseenem@gawab.com>

On Wednesday 14 March 2007 02:35, Ash Milsted wrote:
> Here's my experience with RSDL 0.30 on 2.6.21-rc3-git6 under my normal
> usage scenarios...
>
> Plain desktop use (web browsing, music, etc): no noticeable change
>
> Desktop use during kernel compile (no -j): The compile impacts desktop
> use more with RSDL, but this is easily solved by nice-ing the compile
> (default nice of 10 seems enough). The kind of impact I am talking about
> is e.g. occasional delays in scrolling in the browser etc.
>
> Desktop use whilst talking on Wengophone (run at nice -5): Under RSDL
> some GUI use e.g. opening a new folder in nautilus causes pops (buffer
> underruns) which do not occur with mainline. I suppose the changes in
> RSDL might require a lower nice value for equivalent performance, but
> (as a user) I am limited to -5.
>
> Low-latency audio with JACK and Ardour2: Rock-solid performance with
> either scheduler.. realtime works nicely.
>
> Playing Quake3 (proprietary nvidia driver): Plays smoothly for both
> schedulers.
>
> So, I suppose I'd like to know what to do about the Wengophone issue,
> because that really is a problem for me. I guess your re-worked -ive
> nice values might help?

Well the change to -nice values was to minimise the harm they do to everything 
else. They will still get the lowest latencies and the most cpu but no more 
than previously. The difference will be to more niced tasks. I'm not sure 
just how much cpu you require for wengophone because at -5 it would be 
getting a fair chunk of cpu with the RSDL 0.30. Anyway, by sheer coincidence 
I just emailed out that patch I was planning so feel free to try it.

-- 
-ck

  reply	other threads:[~2007-03-13 15:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-11 23:58 RSDL v0.30 cpu scheduler for mainline kernels Con Kolivas
2007-03-12 23:46 ` David Miller
2007-03-13  3:05   ` Con Kolivas
2007-03-13  4:32     ` Willy Tarreau
2007-03-13  5:03       ` [ck] " Felipe Alfaro Solana
2007-03-13  5:29       ` David Miller
2007-03-13 13:10       ` [ck] " michael chang
2007-03-13 15:35 ` [ck] " Ash Milsted
2007-03-13 15:46   ` Con Kolivas [this message]
2007-03-13 15:53   ` Lee Revell
2007-03-13 17:45     ` Chris Friesen
2007-03-13 20:02       ` Lee Revell
2007-03-14  9:47       ` Ash Milsted
2007-03-15  2:31 ` Siddha, Suresh B
2007-03-15  6:05   ` Con Kolivas
2007-03-15 17:46     ` Siddha, Suresh B
2007-03-15 18:58       ` Ray Lee
2007-03-15 21:11         ` Con Kolivas
2007-03-15 21:12         ` Siddha, Suresh B
2007-03-17 14:27 ` Szonyi Calin

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=200703140246.26522.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thatistosayiseenem@gawab.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