linux-kernel - Re: [Priority Inheritance] SCHED_FIFO or SCHED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOVSwNH=K796hrtPkGh_y47gbkC+f_Cn+_CqBX-ozPtmQ3KfDA@mail.gmail.com>
Date:	Sat, 1 Oct 2011 22:31:03 +0200
From:	"Tadeus (Eus) Prastowo" <0x657573@...glemail.com>
To:	Mike Galbraith <efault@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Priority Inheritance] SCHED_FIFO or SCHED_RR?

On Sat, Oct 1, 2011 at 10:29 PM, Tadeus (Eus) Prastowo
<0x657573@...glemail.com> wrote:
> For the case of one SCHED_RR task sharing a critical section with one
> SCHED_NORMAL task, the worst-case blocking time of the SCHED_RR task
> is found by multiplying the critical section execution time taking
> into account the slice by two.

Sorry, the worst-case blocking time is just the critical section
execution time taking into account the slice.

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