public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Freitas <miguel@cetuc.puc-rio.br>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: 12 Jul 2003 16:13:46 -0300	[thread overview]
Message-ID: <1058037226.1196.122.camel@mf> (raw)
In-Reply-To: <Pine.LNX.4.55.0307120922450.4351@bigblue.dev.mcafeelabs.com>

On Sat, 2003-07-12 at 13:30, Davide Libenzi wrote:
> > > Patch acceptance is
> > > tricky and definitely would need more discussion and test.
> >
> > Sure. But let me add a voice of support here: I would be great if kernel
> > provided a way to multimedia or interactive applications to request a
> > better latency predictability (or hint the scheduler somehow) without
> > need of being root. If that comes in a form of a new scheduler policy,
> > or just allowing small negative nice values for non-root i don't mind...
> 
> You'd need a nice value that will keep you away from being caught by
> interactive SCHED_OTHER. Otherwise yes, this is another solution. Did you
> try it with xine under high load ?

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.

regards,

Miguel


  reply	other threads:[~2003-07-12 18:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 13:43 [patch] SCHED_SOFTRR linux scheduler policy 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 [this message]
2003-07-12 20:07         ` Davide Libenzi
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=1058037226.1196.122.camel@mf \
    --to=miguel@cetuc.puc-rio.br \
    --cc=davidel@xmailserver.org \
    --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