mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: "Tadeus (Eus) Prastowo" <0x657573@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Priority Inheritance] SCHED_FIFO or SCHED_RR?
Date: Sun, 02 Oct 2011 09:50:07 +0200	[thread overview]
Message-ID: <1317541807.6176.120.camel@marge.simson.net> (raw)
In-Reply-To: <CAOVSwNEQzhzoKwnW5dZn8YsL5G+80_yvodmeJKBs2dSAxn7MsQ@mail.gmail.com>

On Sat, 2011-10-01 at 22:29 +0200, Tadeus (Eus) Prastowo wrote:
> On Sat, Oct 1, 2011 at 7:41 AM, Mike Galbraith <efault@gmx.de> wrote:
> > On Fri, 2011-09-30 at 21:12 +0200, Tadeus (Eus) Prastowo wrote:
> >> > Why should a SCHED_NORMAL task inheriting the priority of a SCHED_RR
> >> > task get the privilege of SCHED_FIFO task for running as long as it
> >> > wishes even when the task giving the inheritance does not have such
> >> > privilege?
> >
> > Existence of a critical section > slice would be the real problem, no?
> 
> No, it's not a problem because if a real-time system designer puts a
> real-time task under SCHED_RR, he will calculate the length of the
> critical section by taking into account the slice.

Submit a patch, and see if it flies.

	-Mike


  parent reply	other threads:[~2011-10-02  7:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 23:06 Tadeus (Eus) Prastowo
2011-09-28 12:38 ` Tadeus (Eus) Prastowo
2011-09-30 19:12 ` Tadeus (Eus) Prastowo
2011-10-01  5:41   ` Mike Galbraith
2011-10-01 20:29     ` Tadeus (Eus) Prastowo
2011-10-01 20:31       ` Tadeus (Eus) Prastowo
2011-10-02  7:50       ` Mike Galbraith [this message]
2011-10-02 15:32         ` Tadeus (Eus) Prastowo

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=1317541807.6176.120.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=0x657573@googlemail.com \
    --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

Powered by JetHome