linux-kernel - Re: Issue in PI boosting code in __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] [day] [month] [year] [list]

Message-ID: <CAMJ=MEewurGHb60mqsMFgpuA6wNguhUM79NDBj=+ygVzY7RpAw@mail.gmail.com>
Date:	Thu, 7 May 2015 22:25:19 +0200
From:	Ronny Meeus <ronny.meeus@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mike Galbraith <umgwanakikbuti@...il.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Issue in PI boosting code in __sched_setscheduler

On Thu, May 7, 2015 at 10:22 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 7 May 2015 22:17:48 +0200
> Ronny Meeus <ronny.meeus@...il.com> wrote:
>
>> > View on what?
>>
>> Whether the real-time priority threads are used a lot.
>> I have the impression that there are severe issues in the Linux eco
>> system (Kernel+glibc) when it comes to real-time priority handling.
>>
>
> It matters what you want from the thread. Real-time is about
> determinism, not throughput. Most actions are about throughput, so it
> would not surprise me that they do not make them RT.
>

OK I understand.
I will try to test the patch of Thomas tomorrow.

Thanks Steve and Thomas for solving this issue.

> -- Steve
--
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/