home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat2 / standard / sched_getparam.z / sched_getparam
Encoding:
Text File  |  2001-04-17  |  3.9 KB  |  66 lines
  1.  
  2.  
  3.  
  4. sssscccchhhheeeedddd____ggggeeeettttppppaaaarrrraaaammmm((((2222))))                                            sssscccchhhheeeedddd____ggggeeeettttppppaaaarrrraaaammmm((((2222))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm - get the scheduling parameters of a process
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<sssscccchhhheeeedddd....hhhh>>>>
  13.      _iiii_nnnn_tttt _ssss_cccc_hhhh_eeee_dddd______gggg_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______gggg_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm system call is used to get the scheduling parameters
  17.      for the process specified by _p_i_d.  If _p_i_d is set to zero, then the
  18.      scheduling parameters of the calling process will be obtained.
  19.  
  20.      A process may obtain the scheduling parameters of itself and any process
  21.      sharing the same real user ID [see _gggg_eeee_tttt_uuuu_iiii_dddd(2)].  To obtain the scheduling
  22.      parameters of an unrelated process, the calling process must have the
  23.      CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT capability [see _c_a_p_a_b_i_l_i_t_y].
  24.  
  25.      The scheduling parameters of _p_i_d are returned via the parameter structure
  26.      at address _p_a_r_a_m (see _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm(2)).
  27.  
  28.      If _p_i_d refers to a POSIX thread process [see _pppp_tttt_hhhh_rrrr_eeee_aaaa_dddd_ssss(3P)] then this call
  29.      retrieves the scheduling policy parameters that are shared by process
  30.      scope and bound scope threads.
  31.  
  32.      _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_pppp_aaaa_rrrr_aaaa_mmmm will fail if one or more of the following are true:
  33.  
  34.      [EINVAL]       The process specified by _p_i_d is not executing with a
  35.                     scheduling policy.
  36.  
  37.      [EFAULT]       The address specified by _p_a_r_a_m is outside the range of the
  38.                     address space of the calling process.
  39.  
  40.      [EPERM]        The calling process attempted to obtain the scheduling
  41.                     parameters of an unrelated process and the caller does not
  42.                     have the CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT capability.
  43.  
  44.      [ESRCH]        The process specified by _p_i_d does not exist.
  45.  
  46. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  47.      capability(4), sched_getscheduler(2), sched_get_priority_max(2),
  48.      sched_get_priority_min(2), sched_rr_get_interval(2), sched_setparam(2),
  49.      sched_setscheduler(2), sched_yield(2), getuid(2), pthreads(5)
  50.  
  51. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  52.      Upon successful completion, a value of 0 is returned to the calling
  53.      process. Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to
  54.      indicate the error.
  55.  
  56.  
  57.  
  58.  
  60.  
  61.  
  62.                                                                         PPPPaaaaggggeeee 1111
  63.  
  64.  
  65.  
  66.