From: Max Krasnyanskiy <maxk@qualcomm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
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 10:04:46 -0800 [thread overview]
Message-ID: <47A9F6BE.1010800@qualcomm.com> (raw)
In-Reply-To: <1202297381.19243.48.camel@lappy>
Peter Zijlstra wrote:
> 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.
Yes. That's what I meant. I don't think overall per process setting is that useful.
Per thread though would be useful.
How to expose that to the user-space ? The best option in my opinion is to extend
struct sched_param. That way both sched_setparam() and pthread_attr_setschedparam()
can be used to set new attributes and it's backwards compatible.
Something like:
struct sched_param {
...
unsigned int sched_rt_limit;
unsigned int sched_rt_...;
};
Max
next prev parent reply other threads:[~2008-02-06 18:06 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
2008-02-06 18:04 ` Max Krasnyanskiy [this message]
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=47A9F6BE.1010800@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--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.