From: Davide Libenzi <davidel@xmailserver.org>
To: Miguel Freitas <miguel@cetuc.puc-rio.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: Sat, 12 Jul 2003 13:07:05 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0307121303060.4720@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <1058037226.1196.122.camel@mf>
On Sat, 12 Jul 2003, Miguel Freitas wrote:
> On Sat, 2003-07-12 at 13:30, Davide Libenzi wrote:
> Since i upgraded my computer recently it's difficult to compare with the
> experiments i made before. But basically no, i haven't tried to make
> xine smooth under high load. my primary complain was that even a small
> background load caused by KSysGuard (KDE system monitor) could make it
> drop frames from time to time. with nice values like -2 the problem was
> completely fixed.
IMMIC (If My Math Is Correct :) you would need a nice -11 to be completely
sure that your task will not be preempted by an iteractive SCHED_OTHER
(one can go to +5 and the other might go to -5) with the current settings.
- Davide
next prev parent reply other threads:[~2003-07-12 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 13:43 Miguel Freitas
2003-07-12 15:20 ` Davide Libenzi
2003-07-12 15:49 ` Jamie Lokier
2003-07-12 15:59 ` Davide Libenzi
2003-07-12 16:20 ` Jamie Lokier
2003-07-12 16:18 ` Davide Libenzi
2003-07-12 16:41 ` Miguel Freitas
2003-07-12 18:51 ` Jamie Lokier
2003-07-13 1:44 ` Davide Libenzi
2003-07-13 14:11 ` Jamie Lokier
2003-07-13 17:15 ` Davide Libenzi
2003-07-12 22:42 ` Bill Huey
2003-07-13 2:39 ` Davide Libenzi
2003-07-13 3:59 ` Bill Huey
2003-07-12 16:34 ` Miguel Freitas
2003-07-12 16:30 ` Davide Libenzi
2003-07-12 19:13 ` Miguel Freitas
2003-07-12 20:07 ` Davide Libenzi [this message]
2003-07-12 18:44 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 2:33 Davide Libenzi
2003-07-13 11:50 ` Pavel Machek
2003-07-13 11:53 ` Alan Cox
2003-07-13 16:08 ` Davide Libenzi
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=Pine.LNX.4.55.0307121303060.4720@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel@cetuc.puc-rio.br \
/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®