All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Robert Love <rml@tech9.net>
Cc: Helge Hafting <helgehaf@aitel.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scheduler hints
Date: Fri, 7 Jun 2002 13:32:31 +0200	[thread overview]
Message-ID: <20020607113231.GA133@elf.ucw.cz> (raw)
In-Reply-To: <1023206034.912.89.camel@sinai> <3CFDC796.C05FC7E2@aitel.hist.no> <1023293838.917.283.camel@sinai>

Hi!

> > Seems to me this particular case is covered by increasing
> > priority when grabbing the semaphore and normalizing
> > priority when releasing.  
> > 
> > Only root can do that - but only root does real-time
> > anyway. And I guess only rood should be able to increase 
> > its timeslice too...
> 
> Increasing its priority has no bearing on whether it runs out of
> timeslice, however.  The idea here is to help the task complete its
> critical section (and thus not block other tasks) before being
> preempted.  Only way to achieve that is boost its timeslice.
> 
> Boosting its priority will assure there is no priority inversion and
> that, eventually, the task will run - but it does nothing to avoid the
> nasty "grab resource, be preempted, reschedule a bunch, finally find
> yourself running again since everyone else blocked" issue.
> 
> And I don't think only root should be able to do this.  If we later
> punish the task (take back the timeslice we gave it) then this is
> fair.

Another possibility might be to allow it to *steal* time from another
processes... Of course only processes of same UID ;-).
									Pavel
-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

  reply	other threads:[~2002-06-07 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:53 [PATCH] scheduler hints Robert Love
2002-06-04 17:38 ` Simon Trimmer
2002-06-04 18:07   ` Robert Love
2002-06-05  8:11 ` Helge Hafting
2002-06-05 10:23   ` Dave Jones
2002-06-05 16:17   ` Robert Love
2002-06-07 11:32     ` Pavel Machek [this message]
2002-06-12 18:37       ` Ingo Oeser
2002-06-12 19:39         ` Robert Love
     [not found] <no.id>
2002-06-06  0:46 ` Rick Bressler
2002-06-06  0:53   ` Robert Love
2002-06-06  1:14     ` Rick Bressler
2002-06-06  1:05   ` Gerrit Huizenga
2002-06-06  1:11     ` Robert Love
2002-06-06  1:19       ` Gerrit Huizenga
2002-06-10 21:05   ` Bill Davidsen
2002-06-10 22:27     ` Gerrit Huizenga

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=20020607113231.GA133@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.