mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, a.p.zijlstra@chello.nl
Subject: Re: [RESEND][RFC v3 PATCH] RTTIME watchdog timer proc interface
Date: Thu, 3 Apr 2008 16:11:06 -0700	[thread overview]
Message-ID: <20080403161106.fe260fd7.akpm@linux-foundation.org> (raw)
In-Reply-To: <47F55D8D.3060700@ct.jp.nec.com>

On Thu, 03 Apr 2008 15:43:25 -0700
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> wrote:

> From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> 
> Introduce new proc interface for RTTIME watchdog.
> It makes administrator able to set RTTIME watchdog to exisiting real-time
> applications without impact. It's useful we don't want to change software
> stack, but want to use RTTIME watchdog for that software.

Well you don't really need to change the software stack.  It's a matter of
setting RLIMIT_RTTIME in the parent process before starting the stack up. 
This is not much more work than poking at /proc/<pid>/rttime afterwards.

Although setting RLIMIT_RTTIME via fork() is much less useful than being
able to alter it at runtime.

>  fs/proc/base.c |  103 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++

And that's rather a lot of new code just for RLIMIT_RTTIME.  And
RLIMIT_RTTIME is not the only rlimit which has this problem - generally the
rlimit interface is a rather nasty one.


I think we should look at creating a general way of modifying and reading a
running process's rlimits.  If we want to do that, a syscall would be the
appropriate interface.


  reply	other threads:[~2008-04-03 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 22:43 Hiroshi Shimamoto
2008-04-03 23:11 ` Andrew Morton [this message]
2008-04-03 23:48   ` Hiroshi Shimamoto

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=20080403161106.fe260fd7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=h-shimamoto@ct.jp.nec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome