Among these two in my ps output, which real-time process will be preempted over the other by linux?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












I have got some idea from: https://stackoverflow.com/questions/8887531/which-real-time-priority-is-the-highest-priority-in-linux about how the real time priority values assigned to different identifiers in the kernel mean different (opposite) things.



But I'm still not clear on the interpretation of values in the RTPRIO column of my ps output. Does higher numerical value mean higher priority or is it the opposite.



Specifically, given ps ouput below: whether rcub/0 (RTPRIO=1) is higher priority than (i.e. can preempt) migration/0 (RTPRIO=99) or is it the other way around.



enter image description here










share|improve this question

























    up vote
    2
    down vote

    favorite












    I have got some idea from: https://stackoverflow.com/questions/8887531/which-real-time-priority-is-the-highest-priority-in-linux about how the real time priority values assigned to different identifiers in the kernel mean different (opposite) things.



    But I'm still not clear on the interpretation of values in the RTPRIO column of my ps output. Does higher numerical value mean higher priority or is it the opposite.



    Specifically, given ps ouput below: whether rcub/0 (RTPRIO=1) is higher priority than (i.e. can preempt) migration/0 (RTPRIO=99) or is it the other way around.



    enter image description here










    share|improve this question























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I have got some idea from: https://stackoverflow.com/questions/8887531/which-real-time-priority-is-the-highest-priority-in-linux about how the real time priority values assigned to different identifiers in the kernel mean different (opposite) things.



      But I'm still not clear on the interpretation of values in the RTPRIO column of my ps output. Does higher numerical value mean higher priority or is it the opposite.



      Specifically, given ps ouput below: whether rcub/0 (RTPRIO=1) is higher priority than (i.e. can preempt) migration/0 (RTPRIO=99) or is it the other way around.



      enter image description here










      share|improve this question













      I have got some idea from: https://stackoverflow.com/questions/8887531/which-real-time-priority-is-the-highest-priority-in-linux about how the real time priority values assigned to different identifiers in the kernel mean different (opposite) things.



      But I'm still not clear on the interpretation of values in the RTPRIO column of my ps output. Does higher numerical value mean higher priority or is it the opposite.



      Specifically, given ps ouput below: whether rcub/0 (RTPRIO=1) is higher priority than (i.e. can preempt) migration/0 (RTPRIO=99) or is it the other way around.



      enter image description here







      process ps real-time priority






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 hours ago









      explorest

      297128




      297128




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote













          According to proc man:



          Priority is the amount of time that a process waited-for children have been scheduled in kernel mode, it is measured in clock ticks. A value in the range 19 (low priority) to -20 (high priority). Process can be running under real-time or non-real time priorities.



          • For processes running a real-time scheduling policy (i.e. the scheduler is the kernel component that decides which runnable process will be executed by the CPU next. Each process has an associated scheduling policy and a static scheduling priority, sched_priority; these are the settings that are modified by sched_setscheduler(). The scheduler makes it decisions based on knowledge of the scheduling policy and static priority of all processes on the system.), this is the negated scheduling priority, minus one; that is, a number in the range -2 to -100, corresponding to real-time priorities 1 to 99.

          • For processes running under a non-real-time scheduling policy, this is the raw nice value (i.e. the scheduling priority of the process, process group, or user, as indicated by which and who is obtained with the getpriority() call and set with the setpriority() call.) as represented in the kernel. The kernel stores nice values (i.e. column NI in the ps table as numbers in the range 0 (high) to 39 (low), corresponding to the user-visible nice range of -20 to 19.





          share|improve this answer






















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471963%2famong-these-two-in-my-ps-output-which-real-time-process-will-be-preempted-over%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            4
            down vote













            According to proc man:



            Priority is the amount of time that a process waited-for children have been scheduled in kernel mode, it is measured in clock ticks. A value in the range 19 (low priority) to -20 (high priority). Process can be running under real-time or non-real time priorities.



            • For processes running a real-time scheduling policy (i.e. the scheduler is the kernel component that decides which runnable process will be executed by the CPU next. Each process has an associated scheduling policy and a static scheduling priority, sched_priority; these are the settings that are modified by sched_setscheduler(). The scheduler makes it decisions based on knowledge of the scheduling policy and static priority of all processes on the system.), this is the negated scheduling priority, minus one; that is, a number in the range -2 to -100, corresponding to real-time priorities 1 to 99.

            • For processes running under a non-real-time scheduling policy, this is the raw nice value (i.e. the scheduling priority of the process, process group, or user, as indicated by which and who is obtained with the getpriority() call and set with the setpriority() call.) as represented in the kernel. The kernel stores nice values (i.e. column NI in the ps table as numbers in the range 0 (high) to 39 (low), corresponding to the user-visible nice range of -20 to 19.





            share|improve this answer


























              up vote
              4
              down vote













              According to proc man:



              Priority is the amount of time that a process waited-for children have been scheduled in kernel mode, it is measured in clock ticks. A value in the range 19 (low priority) to -20 (high priority). Process can be running under real-time or non-real time priorities.



              • For processes running a real-time scheduling policy (i.e. the scheduler is the kernel component that decides which runnable process will be executed by the CPU next. Each process has an associated scheduling policy and a static scheduling priority, sched_priority; these are the settings that are modified by sched_setscheduler(). The scheduler makes it decisions based on knowledge of the scheduling policy and static priority of all processes on the system.), this is the negated scheduling priority, minus one; that is, a number in the range -2 to -100, corresponding to real-time priorities 1 to 99.

              • For processes running under a non-real-time scheduling policy, this is the raw nice value (i.e. the scheduling priority of the process, process group, or user, as indicated by which and who is obtained with the getpriority() call and set with the setpriority() call.) as represented in the kernel. The kernel stores nice values (i.e. column NI in the ps table as numbers in the range 0 (high) to 39 (low), corresponding to the user-visible nice range of -20 to 19.





              share|improve this answer
























                up vote
                4
                down vote










                up vote
                4
                down vote









                According to proc man:



                Priority is the amount of time that a process waited-for children have been scheduled in kernel mode, it is measured in clock ticks. A value in the range 19 (low priority) to -20 (high priority). Process can be running under real-time or non-real time priorities.



                • For processes running a real-time scheduling policy (i.e. the scheduler is the kernel component that decides which runnable process will be executed by the CPU next. Each process has an associated scheduling policy and a static scheduling priority, sched_priority; these are the settings that are modified by sched_setscheduler(). The scheduler makes it decisions based on knowledge of the scheduling policy and static priority of all processes on the system.), this is the negated scheduling priority, minus one; that is, a number in the range -2 to -100, corresponding to real-time priorities 1 to 99.

                • For processes running under a non-real-time scheduling policy, this is the raw nice value (i.e. the scheduling priority of the process, process group, or user, as indicated by which and who is obtained with the getpriority() call and set with the setpriority() call.) as represented in the kernel. The kernel stores nice values (i.e. column NI in the ps table as numbers in the range 0 (high) to 39 (low), corresponding to the user-visible nice range of -20 to 19.





                share|improve this answer














                According to proc man:



                Priority is the amount of time that a process waited-for children have been scheduled in kernel mode, it is measured in clock ticks. A value in the range 19 (low priority) to -20 (high priority). Process can be running under real-time or non-real time priorities.



                • For processes running a real-time scheduling policy (i.e. the scheduler is the kernel component that decides which runnable process will be executed by the CPU next. Each process has an associated scheduling policy and a static scheduling priority, sched_priority; these are the settings that are modified by sched_setscheduler(). The scheduler makes it decisions based on knowledge of the scheduling policy and static priority of all processes on the system.), this is the negated scheduling priority, minus one; that is, a number in the range -2 to -100, corresponding to real-time priorities 1 to 99.

                • For processes running under a non-real-time scheduling policy, this is the raw nice value (i.e. the scheduling priority of the process, process group, or user, as indicated by which and who is obtained with the getpriority() call and set with the setpriority() call.) as represented in the kernel. The kernel stores nice values (i.e. column NI in the ps table as numbers in the range 0 (high) to 39 (low), corresponding to the user-visible nice range of -20 to 19.






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 2 hours ago

























                answered 2 hours ago









                Goro

                5,01552459




                5,01552459



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471963%2famong-these-two-in-my-ps-output-which-real-time-process-will-be-preempted-over%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Comments

                    Popular posts from this blog

                    Long meetings (6-7 hours a day): Being “babysat” by supervisor

                    Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

                    Confectionery