From: "Ulrich Drepper" <drepper@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>,
"Ulrich Drepper" <drepper@gmail.com>,
"Bill Irwin" <bill.irwin@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Eric Dumazet" <dada1@cosmosbay.com>,
linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: per-thread rusage
Date: Tue, 1 May 2007 17:17:28 -0700 [thread overview]
Message-ID: <a36005b50705011717g28023c58m431ec28413c1b613@mail.gmail.com> (raw)
In-Reply-To: <20070501222724.GG26093@thunk.org>
On 5/1/07, Theodore Tso <tytso@mit.edu> wrote:
> There are two ways of implementing this. One is to have the
> JVM periodically poll using a pthread_getrusage() interface.
Not a good idea.
> A better
> choice might be some kind of per-thread CPU limit, that would result
> in a thread-specific SIGXCPU signal. But there are no interfaces
> today that do anything like this.
We have, in principal: setrlimit. We jump through hoops in the moment
to make RLIMIT_CPU a per-process facility. This is all nice. All you
need to do is to add resources RLIMIT_*_THREAD (e.g.,
RLIMIT_CPU_THREAD) and additionally do accounting in a per-thread
basis.
The only issue which has to be decided is what is the action when the
limit is exceeded. An unanswered signal kills the process, not just
the thread. And you cannot just terminate a thread in the kernel
since there might be userlevel cleanup to do. The thread library can
also not simply hijack the SIGXCPU signal, the application want to use
it. The thread cancellation must appear like any other cancellation,
perhaps with a special status value (PTHREAD_CANCELED_XCPU instead of
PTHREAD_CANCEL). But that's a userlevel detail.
So what would be additionally needed is a method to specify what
signal to sent. The default might just as well be SIGXCPU but this
must be changable.
next prev parent reply other threads:[~2007-05-02 0:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 17:29 William Lee Irwin III
2007-04-04 17:48 ` Eric Dumazet
2007-04-04 18:10 ` William Lee Irwin III
2007-04-09 23:53 ` Andrew Morton
2007-04-10 0:42 ` William Lee Irwin III
2007-04-10 0:53 ` Andrew Morton
2007-04-10 1:12 ` William Lee Irwin III
2007-04-10 1:18 ` Andrew Morton
2007-05-01 17:29 ` Bill Irwin
2007-05-01 18:39 ` Ulrich Drepper
2007-05-01 20:24 ` Bill Irwin
2007-05-01 22:10 ` Ulrich Drepper
2007-05-01 22:27 ` Theodore Tso
2007-05-01 22:34 ` Bill Irwin
2007-05-01 23:04 ` Alan Cox
2007-05-01 23:17 ` Bill Irwin
2007-05-02 5:05 ` Balbir Singh
2007-05-02 0:17 ` Ulrich Drepper [this message]
2007-05-02 4:31 ` Theodore Tso
2007-05-02 4:57 ` Ulrich Drepper
2007-05-01 22:29 ` Bill Irwin
2007-04-04 22:36 ` Valdis.Kletnieks
2007-04-05 4:09 ` William Lee Irwin III
2007-04-10 20:10 Oleg Nesterov
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=a36005b50705011717g28023c58m431ec28413c1b613@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bill.irwin@oracle.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wli@holomorphy.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®