From: "Lee Revell" <rlrevell@joe-job.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: "Ash Milsted" <thatistosayiseenem@gawab.com>,
"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 16:02:23 -0400 [thread overview]
Message-ID: <75b66ecd0703131302j32d58e7do5b0811e13c170c17@mail.gmail.com> (raw)
In-Reply-To: <45F6E34E.9020308@nortel.com>
On 3/13/07, Chris Friesen <cfriesen@nortel.com> wrote:
> Lee Revell wrote:
>
> > Sounds like Wengophone is broken. It should be using RT threads for
> > time critical work, as JACK and Ardour2 are doing.
>
> If the app has root privileges to set RT policy, then it could also set
> deeply negative nice values as well.
>
> Doesn't reallly help the regular user with no privileges.
Well this was supposed to be solved by RLIMIT_NICE and RLIMIT_RTPRIO
which went into mainline about a year ago but distros have been very
slow to pick up the new PAM, glibc and bash packages. We don't have a
clear picture yet of what defaults the distros will ship.
Lee
next prev parent reply other threads:[~2007-03-13 20:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 23:58 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
2007-03-13 17:45 ` Chris Friesen
2007-03-13 20:02 ` Lee Revell [this message]
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=75b66ecd0703131302j32d58e7do5b0811e13c170c17@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=cfriesen@nortel.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
Powered by JetHome