From: Mike Galbraith <efault@gmx.de>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]O14int [SCHED_SOFTRR please]
Date: Mon, 11 Aug 2003 21:46:00 +0200 [thread overview]
Message-ID: <5.2.1.1.2.20030811212837.01975fa0@pop.gmx.net> (raw)
In-Reply-To: <200308112019.38613.roger.larsson@skelleftea.mail.telia.com >
At 08:19 PM 8/11/2003 +0200, Roger Larsson wrote:
>On Sunday 10 August 2003 13.17, Mike Galbraith wrote:
> > At 01:48 AM 8/10/2003 -0700, Simon Kirby wrote:
> > >I am seeing similar starvation problems that others are seeing in these
> > >threads. At first it was whenever I clicked a link in Mozilla -- xmms
> > >would stop, sometimes for a second or so, on a Celeron 466 MHz machine.
> >
> > Do you see this with test-X and Ingo's latest changes too? I can only
> > imagine one scenario off the top of my head where this could happen; if
> > xmms exhausted a slice while STARVATION_LIMIT is exceeded, it could land in
> > the expired array and remain unserviced for the period of time it takes for
> > all tasks remaining in the active array to exhaust their slices. Seems
> > like that should be pretty rare though.
> >
>
>xmms is a RT process - it does not really have interactivity problems...
>It will be extremely hard to fix this in a generic scheduler, instead
>let xmms be the RT process it is with SCHED_SOFTRR (or whatever
>it will be named).
>Do this for arts, and other audio/video path applications.
(For the scenario described, it doesn't matter what scheduler policy is used)
>Then start the race for interactivity tuning
> (X, X applications, console, login, etc)
>
>interactivity = two-way
> http://www.m-w.com/cgi-bin/dictionary?va=interactive
>
>Listening to music is not interactive.
?!? <tilt> What makes you say that? What in the world am I doing when I
fire up xmms?
(can't be the two way thing... that's happening until I stop listening)
-Mike
-Mike
next prev parent reply other threads:[~2003-08-11 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 20:08 [PATCH]O14int Voluspa
2003-08-09 0:36 ` [PATCH]O14int Con Kolivas
2003-08-10 8:48 ` [PATCH]O14int Simon Kirby
2003-08-10 9:06 ` [PATCH]O14int Con Kolivas
2003-08-12 17:56 ` [PATCH]O14int Simon Kirby
2003-08-12 21:21 ` [PATCH]O14int Con Kolivas
2003-08-10 10:08 ` [PATCH]O14int William Lee Irwin III
2003-08-12 18:36 ` [PATCH]O14int Simon Kirby
2003-08-10 11:17 ` [PATCH]O14int Mike Galbraith
2003-08-11 18:19 ` [PATCH]O14int [SCHED_SOFTRR please] Roger Larsson
2003-08-11 21:53 ` Con Kolivas
[not found] ` <200308120226.35580.roger.larsson@skelleftea.mail.telia.com >
2003-08-12 5:40 ` What is interactivity? " Mike Galbraith
2003-08-12 15:29 ` Timothy Miller
2003-08-13 1:43 ` Rob Landley
[not found] ` <200308112019.38613.roger.larsson@skelleftea.mail.telia.com >
2003-08-11 19:46 ` Mike Galbraith [this message]
2003-08-12 0:26 ` Roger Larsson
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=5.2.1.1.2.20030811212837.01975fa0@pop.gmx.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@skelleftea.mail.telia.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
all inboxes | Powered by JetHome®