home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / p_man / cat2 / standard / sched_setparam.z / sched_setparam
Encoding:
Text File  |  2002-10-03  |  5.2 KB  |  132 lines
  1.  
  2.  
  3.  
  4. sssscccchhhheeeedddd____sssseeeettttppppaaaarrrraaaammmm((((2222))))                                            sssscccchhhheeeedddd____sssseeeettttppppaaaarrrraaaammmm((((2222))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm - set the scheduling parameters of a process
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<sssscccchhhheeeedddd....hhhh>>>>
  13.      _iiii_nnnn_tttt _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm _((((_pppp_iiii_dddd______tttt _p_i_d_,,,, _cccc_oooo_nnnn_ssss_tttt _ssss_tttt_rrrr_uuuu_cccc_tttt _ssss_cccc_hhhh_eeee_dddd______pppp_aaaa_rrrr_aaaa_mmmm _****_p_a_r_a_m_))))_;;;;
  14.  
  15. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  16.      The _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm system call is used to set the scheduling policy
  17.      parameters for the process specified by _p_i_d.  If _p_i_d is set to zero, then
  18.      the scheduling parameters of the calling process will be affected.
  19.  
  20.      The scheduling parameters of _p_i_d are specified by the parameter structure
  21.      at address _p_a_r_a_m.
  22.  
  23.      The priority of the target process may be modified by setting the desired
  24.      priority value in the sched_priority field of the _p_a_r_a_m structure.
  25.  
  26.      Unlike IRIX 6.2 and earlier releases, processes having a higher numerical
  27.      priority value are more important than processes having a lower numerical
  28.      priority value. Specified priorities remain fixed, unless explicitly
  29.      changed in the future, and are not affected by priority aging schemes.
  30.  
  31.      The priority range for these scheduling policies may be obtained via the
  32.      _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt______pppp_rrrr_iiii_oooo_rrrr_iiii_tttt_yyyy______mmmm_iiii_nnnn(2) and _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt______pppp_rrrr_iiii_oooo_rrrr_iiii_tttt_yyyy______mmmm_aaaa_xxxx(2) function calls.
  33.      However, arbitrary priority values within the range should not be used.
  34.      Developers must consider the needs of the application and how it should
  35.      interact with the rest of the system, before selecting a real-time
  36.      priority.  For more information, see the "Real-Time Priority Band"
  37.      section of _rrrr_eeee_aaaa_llll_tttt_iiii_mmmm_eeee(5).
  38.  
  39.      The calling process must have the CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT capability [see
  40.      _c_a_p_a_b_i_l_i_t_y] to successfully execute _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm.
  41.  
  42.      If the process specified by _p_i_d is currently executing or is in a
  43.      runnable state, _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm causes the process to be rescheduled at
  44.      its new priority.
  45.  
  46.      _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm will fail if one or more of the following are true:
  47.  
  48.      [EINVAL]       One of the specified parameters at address _p_a_r_a_m are out
  49.                     of range or scope.
  50.  
  51.      [EPERM]        The calling process does not have the CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT
  52.                     capability.
  53.  
  54.      [ESRCH]        The process specified by _p_i_d does not exist.
  55.  
  56.  
  57.  
  58.  
  60.  
  61.  
  62.                                                                         PPPPaaaaggggeeee 1111
  63.  
  64.  
  65.  
  66.  
  67.  
  68.  
  69. sssscccchhhheeeedddd____sssseeeettttppppaaaarrrraaaammmm((((2222))))                                            sssscccchhhheeeedddd____sssseeeettttppppaaaarrrraaaammmm((((2222))))
  70.  
  71.  
  72.  
  73. SEE ALSO
  74.      capability(4), realtime(5), sched_getparam(2), sched_getscheduler(2),
  75.      sched_setscheduler(2), sched_yield(2), sched_get_priority_max(2),
  76.      sched_get_priority_min(2), sched_rr_get_interval(2), pthreads(5)
  77.  
  78. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  79.      Upon successful completion, a value of 0 is returned to the calling
  80.      process. Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to
  81.      indicate the error.
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.                                                                         PPPPaaaaggggeeee 2222
  129.  
  130.  
  131.  
  132.