Re: Comments on the KSE option

:No, it is POSIX.  You, the application, can write a program with
:system scope or process scope threads and get whatever you behavior
:you want, within rlimits of course.
:
:If you want unfair scheduling, then create your threads with
:system scope contention, otherwise use process scope.  The
:kernel should be designed to allow both, and have adjustable
:limits in place for (at least) system scope threads.
:
:Noone is saying that you can't have as many system scope threads
:as you want (and as allowed by limits), just that you must also
:be able to have process scope threads (with probably higher limits
:or possibly no limits).
:
:-- 
:DE

    This is a nice concept, but totally unrealistic in actual operation
    because you generally have no control over how the application
    programmer designed his application.  It is the user running the
    application who needs to be able to control how the thread scope
    effects the overall system, not the application designer.   

    The argument here is not how a program runs alone on a system, but how
    it effects the performance of other programs running on the system.

    Unless you are advocating that the system administrator or user perform
    surgery on every single application in the system (KDE, Firefox, and
    on down the line), the problem cannot be solved by depending on 
    programmers to do the right thing vis-a-vie the POSIX standard.

					-Matt