linux-kernel - Re: RT scheduler config, suggestions and questions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 06 Feb 2008 22:50:55 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Max Krasnyanskiy <maxk@...lcomm.com>
Cc:	Steven Rostedt <srostedt@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: RT scheduler config, suggestions and questions


On Wed, 2008-02-06 at 10:04 -0800, Max Krasnyanskiy wrote:
> 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_...;
> };

I'm somewhat afraid to touch sched_param, but it seems I need to change
it anyway soonish, so I'd better figure out how to do that.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/