From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Max Krasnyanskiy <maxk@qualcomm.com>
Cc: Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RT scheduler config, suggestions and questions
Date: Wed, 06 Feb 2008 12:29:40 +0100 [thread overview]
Message-ID: <1202297381.19243.48.camel@lappy> (raw)
In-Reply-To: <1202279815.19243.34.camel@lappy>
On Wed, 2008-02-06 at 07:36 +0100, Peter Zijlstra wrote:
> > btw I can see "watchdog" being very useful to catch hard-RT tasks that exceed the deadline.
> > But's it gotta be per thread.
>
> It is.
>
> > Single setting per user is not enough. Unless a use has a single RT task.
>
> ?
Ah, its starting to make sense, you want it configurable per thread, not
process wide. Yes, I see how that is useful, just no idea how to expose
that to user-space atm.
next prev parent reply other threads:[~2008-02-06 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 23:37 RT scheduler config, suggestions and questions Max Krasnyanskiy
2008-02-06 6:36 ` Peter Zijlstra
2008-02-06 11:29 ` Peter Zijlstra [this message]
2008-02-06 18:04 ` Max Krasnyanskiy
2008-02-06 21:50 ` Peter Zijlstra
2008-02-06 17:52 ` Max Krasnyanskiy
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=1202297381.19243.48.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.