From: "Lee Revell" <rlrevell@joe-job.com>
To: "Ash Milsted" <thatistosayiseenem@gawab.com>
Cc: "Con Kolivas" <kernel@kolivas.org>,
"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: Tue, 13 Mar 2007 11:53:56 -0400 [thread overview]
Message-ID: <75b66ecd0703130853p4c7d029en2405caee4447d29e@mail.gmail.com> (raw)
In-Reply-To: <20070313153514.428dc3e1.thatistosayiseenem@gawab.com>
On 3/13/07, Ash Milsted <thatistosayiseenem@gawab.com> wrote:
> 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.
Sounds like Wengophone is broken. It should be using RT threads for
time critical work, as JACK and Ardour2 are doing.
No scheduler can help if the apps are not correctly written...
Lee
next prev parent reply other threads:[~2007-03-13 15:54 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
2007-03-13 15:53 ` Lee Revell [this message]
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=75b66ecd0703130853p4c7d029en2405caee4447d29e@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@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;
as well as URLs for NNTP newsgroup(s).