> > Below is the draft text that I will add to the getrlimit.2 man page to describe > > RLIMIT_RTTIME. Does it look okay to you? (I will add a pointer in > > sched_setscheduler.2 to this description in getrlimit.2.) > > > > RLIMIT_RTTIME (Since Linux 2.6.25) > > Specifies a limit on the amount of CPU time that a > > process scheduled under a real-time scheduling > > policy may consume without making a blocking sys- > > tem call. For the purpose of this limit, each > > time a process makes a blocking system call, the > > count of its consumed CPU time is reset to zero. > > The CPU time count is not reset if the process > > continues trying to use the CPU but is preempted, > > its time slice expires, or it calls > > sched_yield(2). > > > > Upon reaching the soft limit, the process is sent > > a SIGXCPU signal. If the process catches or > > ignores this signal and continues consuming CPU > > time, then SIGXCPU will be generated once each > > second until the hard limit is reached, at which > > point the process is sent a SIGKILL signal. > > > > The intended use of this limit is to stop a run- > > away real-time process from locking up the system. > > > Looks excellent, thanks! Good -- thanks for checking it over. > Acked-by: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> > > in so far that is applicable to man pages ;-) It works for me. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
