linux-kernel - Re: RFC for a new Scheduling policy/class in the Linux-kernel

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jul 2009 01:27:29 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Douglas Niehaus <niehaus@...c.ku.edu>
CC:	Ted & Syauchen Baker <baker.tlh@...cast.net>,
	"'Peter Zijlstra'" <a.p.zijlstra@...llo.nl>,
	"'Henrik Austad'" <henrik@...tad.us>,
	"'LKML'" <linux-kernel@...r.kernel.org>,
	"'Ingo Molnar'" <mingo@...e.hu>,
	"'Bill Huey'" <billh@...ppy.monkey.org>,
	"'Linux RT'" <linux-rt-users@...r.kernel.org>,
	"'Fabio Checconi'" <fabio@...dalf.sssup.it>,
	"'James H. Anderson'" <anderson@...unc.edu>,
	"'Thomas Gleixner'" <tglx@...utronix.de>,
	"'Ted Baker'" <baker@...fsu.edu>,
	"'Dhaval Giani'" <dhaval.giani@...il.com>,
	"'Noah Watkins'" <jayhawk@....ucsc.edu>,
	"'KUSP Google Group'" <kusp@...glegroups.com>
Subject: Re: RFC for a new Scheduling policy/class in the Linux-kernel

Douglas Niehaus wrote:

>      (1.1) Will the use of system services (system calls) by RT threads 
> need to be explicitly supported by, perhaps, explicitly making the 
> schedulers of *other* threads also using those system calls aware of 
> that and take it into account to make those other tasks non-preemptible 
> while holding system call related locks.
> 
>      (1.2) Can Linux SMP ever support this in an acceptable manner since 
> locks associated with systems services are shared across CPU boundaries. 
> THus, I can isolate a set of RT tasks on a CPU easily, and they are well 
> isolated and can run under strict predictability, *until they use a 
> system call that uses a lock*. Then, the system call is an interaction 
> channel with every other thread on the system using the same system call.


This may be a terminology issue, but I think it would be more correct to
say that the lock is the interaction channel, not the system call, and
it is an interaction channel with every other entity on the system using
the same lock.  Depending on the specific lock, this could be other
userspace tasks, kernel threads, or even hardware interrupt handlers.

This goes back to your first question of which system services an RT
task can use while maintaining schedulability analysis.  Unfortunately
this may be a moving target, since the exact answer depends on what
locks are taken in the underlying kernel implementation.

Chris
--
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/