LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: "Eugene Teo" <eugeneteo@kernel.sg>,
linux-kernel@vger.kernel.org,
"Neil Horman" <nhorman@tuxdriver.com>,
"Ingo Molnar" <mingo@elte.hu>,
linux-man@vger.kernel.org
Subject: Re: RLIMIT_RTTIME documentation for getrlimit.2
Date: Mon, 28 Apr 2008 13:44:23 +0200 [thread overview]
Message-ID: <cfd18e0f0804280444jd558060g6cf5ee7df0248ee1@mail.gmail.com> (raw)
In-Reply-To: <4808D1CC.80103@gmail.com>
Hey Peter,
Ping!
Cheers,
Michael
---------- Forwarded message ----------
From: Michael Kerrisk <mtk.manpages@googlemail.com>
Date: Fri, Apr 18, 2008 at 6:52 PM
Subject: RLIMIT_RTTIME documentation for getrlimit.2
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Eugene Teo <eugeneteo@kernel.sg>, linux-kernel@vger.kernel.org,
Neil Horman <nhorman@tuxdriver.com>, Ingo Molnar <mingo@elte.hu>,
linux-man@vger.kernel.org
Peter,
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.
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
next prev parent reply other threads:[~2008-04-28 11:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 14:59 [PATCH] proc: Add RLIMIT_RTTIME to /proc/<pid>/limits Eugene Teo
2008-02-08 15:10 ` Peter Zijlstra
2008-02-28 15:12 ` Michael Kerrisk
2008-02-28 15:21 ` Peter Zijlstra
2008-02-28 15:44 ` Michael Kerrisk
2008-02-28 15:50 ` Peter Zijlstra
2008-04-11 7:38 ` Michael Kerrisk
2008-04-11 7:45 ` Peter Zijlstra
2008-04-11 8:01 ` Michael Kerrisk
2008-02-29 12:32 ` Neil Horman
2008-04-11 8:56 ` Michael Kerrisk
2008-04-11 9:01 ` Peter Zijlstra
2008-04-11 9:16 ` Michael Kerrisk
2008-04-11 9:21 ` Peter Zijlstra
2008-04-11 9:27 ` Michael Kerrisk
2008-04-11 9:32 ` Peter Zijlstra
2008-04-11 9:38 ` Michael Kerrisk
2008-04-18 16:52 ` RLIMIT_RTTIME documentation for getrlimit.2 Michael Kerrisk
2008-04-28 11:44 ` Michael Kerrisk [this message]
2008-04-28 12:09 ` Peter Zijlstra
2008-04-28 12:14 ` Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfd18e0f0804280444jd558060g6cf5ee7df0248ee1@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=eugeneteo@kernel.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@tuxdriver.com \
--subject='Re: RLIMIT_RTTIME documentation for getrlimit.2' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).