linux-kernel - Re: [RFC][PATCH] Multimedia scheduling class, take 2

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: <4A09B3FE.5030503@sonarnerd.net>
Date:	Tue, 12 May 2009 20:38:06 +0300
From:	Jussi Laako <jussi@...arnerd.net>
To:	Raistlin <raistlin@...ux.it>
CC:	Chris Friesen <cfriesen@...tel.com>,
	Peter Zijlstra <peterz@...radead.org>,
	James Courtier-Dutton <James@...erbug.co.uk>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC][PATCH] Multimedia scheduling class, take 2

Raistlin wrote:
> Well, I'm not sure I can see why, since nor a "SCHED_MM" scheduling
> policy, nor having priorities for SCHED_OTHER (different from nice
> levels) is _not_ POSIX compliant, is it?

It is still accessible through the normal API. POSIX specifies just a
set of standard schedulers and gives OS free choice of defining more.
These are still accessible through the same functions. I could modify
the patch to not introduce a new policy and to just modify the existing
SCHED_OTHER the same way (and AFAIK it would still comply with POSIX), I
just wanted to have these separate for the other changes and to keep the
old behavior intact.

POSIX just defines API where there is concept of policy(int) and
priority(int) and a method to query minimum and maximum priority for
given policy. Then it defines base set of policies, but not their
priority ranges or such.

Your proposal would need introduction of completely new function...

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