| 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
| ||
|
Date: Mon, 12 Oct 2009 23:04:55 +0200 From: Dragoslav Zaric <dragoslav.zaric.kd@...il.com> To: Christoph Lameter <cl@...ux-foundation.org> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Real time kernel This is definition from http://rt.wiki.kernel.org/ ------------------------------------------------------------------------- Real-time applications have operational deadlines between some triggering event and the application's response to that event. To meet these operational deadlines, programmers use real-time operating systems (RTOS) on which the maximum response time can be calculated or measured reliably for the given application and environment. ------------------------------------------------------------------------- So for specific requirements I would not say, you get slower kernel, you get purpose-making kernel, because on these kind of systems you probably do not do anything. It is probably the system that listens and responds to some events. Do you want to say, when using preemption in "normal user mode", Linux works slower then without preemption ? It makes sense, "because the latency of a task only depends on the tasks running at equal or higher priorities, all other tasks can be ignored." (http://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions#What_is_real-time.3F) Thanks -- 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/
Powered by blists - more mailing lists