Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ...

From: Mike Galbraith (efault_at_gmx.de)
Date: 08/09/03

  • Next message: Alan Cox: "Re: 2.6.0-test3 Make defconfig or menuconfig - unchoosables" 
    Date:	Sat, 09 Aug 2003 19:47:27 +0200
To: Daniel Phillips <phillips@arcor.de>

    At 03:05 PM 8/9/2003 +0100, Daniel Phillips wrote:
    >Hi Davide,
    >
    >On Sunday 13 July 2003 22:51, Davide Libenzi wrote:
    > > This should (hopefully) avoid other tasks starvation exploits :
    > >
    > > http://www.xmailserver.org/linux-patches/softrr.html
    >
    > "We will define a new scheduler policy SCHED_SOFTRR that will make the
    > target task to run with realtime priority while, at the same time, we will
    > enforce a bound for the CPU time the process itself will consume."
    >
    >This needs to be a global bound, not per-task, otherwise realtime tasks can
    >starve the system, as others have noted.
    >
    >But the patch has a much bigger problem: there is no way a SOFTRR task can be
    >realtime as long as higher priority non-realtime tasks can preempt it. The
    >new dynamic priority adjustment makes it certain that we will regularly see
    >normal tasks with priority elevated above so-called realtime tasks. Even
    >without dynamic priority adjustment, any higher priority system task can
    >unwttingly make a mockery of realtime schedules.

    Not so. Dynamic priority adjustment will not put a SCHED_OTHER task above
    SCHED_RR, SCHED_FIFO or SCHED_SOFTRR, so they won't preempt. Try
    this. Make a SCHED_FIFO task loop, then try to change vt's. You won't
    ever get there from here unless you have made 'events' a higher priority
    realtime task than your SCHED_FIFO cpu hog. (not equal, must be higher
    because SCHED_FIFO can't be requeued via timeslice expiration... since it
    doesn't have one)

    I do see ~problems with this idea though...

    1. SCHED_SOFTRR tasks can disturb (root) SCHED_RR/SCHED_FIFO tasks as is.
    SCHED_SOFTRR should probably be a separate band, above SCHED_OTHER, but
    below realtime queues.

    2. It's not useful for video (I see no difference between realtime
    component of video vs audio), and if the cpu restriction were opened up
    enough to become useful, you'd end up with ~pure SCHED_RR, which you can no
    way allow Joe User access to. As a SCHED_LOWLATENCY, it seems like it
    might be useful, but I wonder how useful.

             -Mike

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Alan Cox: "Re: 2.6.0-test3 Make defconfig or menuconfig - unchoosables"

    Relevant Pages

    • Re: What level of timesynch error is typical on Win XP?
      ... The ping time to the server is 2 milliseconds from ... NTP is being allowed to choose its own polling ... realtime, running the daemon at high realtime priority greatly reduces ...
      (comp.protocols.time.ntp)
    • Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ...
      ... >> target task to run with realtime priority while, at the same time, we ... Even without dynamic priority adjustment, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Windows ntpd highest priority doesnt require admin access
      ... ntpd on Windows attempts to raise itself to the realtime priority ... high priority class instead. ... special privilege to raise priority to realtime, ... Meinberg's installer adds the needed privilege for us. ...
      (comp.protocols.time.ntp)
    • thread priority below and above 15 in the same process?
      ... showing me the real priority of all threads. ... I have run our application process as RealTime, ... I'm aware that I can set threads to THREAD_PRIORITY_LOWEST to get priority ... The app does data aqusition that cannot be run in a normal priority without ...
      (microsoft.public.win32.programmer.kernel)
    • Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ...
      ... enforce a bound for the CPU time the process itself will consume." ... This needs to be a global bound, not per-task, otherwise realtime tasks can ... realtime as long as higher priority non-realtime tasks can preempt it. ...
      (Linux-Kernel)