<?xml version="1.0" encoding='ISO-8859-1'?>
<!--DOCTYPE component PUBLIC "-//OCERA//DTD component XML V1.0//EN" "file:component.dtd"-->

<component id="sa-rtl" name="Stand-Alone RTLinux">
  <title>Stand-Alone RTLinux</title>
  <info>
    <authorgroup>
      <author>
	<firstname>Vicente</firstname>
	<surname>Esteve</surname>
	<affiliation>
	  <orgname>UPVLC</orgname>
	</affiliation>
	<email><ulink url="mailto:viesllo@disca.upv.es">viesllo@disca.upv.es</ulink></email>
      </author>
    </authorgroup>
    
    <reviewergroup>
      <author>
	<firstname>Ismael</firstname>
	<surname>Ripoll</surname>
	<affiliation>
	  <orgname>UPVLC</orgname>
	</affiliation>
	<email><ulink url="mailto:iripoll@disca.upv.es">iripoll@disca.upv.es</ulink></email>
      </author>
    </reviewergroup>

    <copyright>
      <year>2003</year>
      <holder>OCERA Consortium</holder>
    </copyright>

    <deliverable file="ms4-month24/WP5/D5.4.pdf" />
    <workpackage id="WP5" />

    <date start="01/01/2003" release="01/07/2003"/>
    <version cvs="sched/sartl" value="2.0"/>
    <notice>This component can be used outside of the OCERA framework.
    </notice>
    <status value="Stable"/>

   <licenses>
    <license name="MPL" />
    <license name="GPL" />
    <license name="LGPL" />
    <license name="CeCILL" file="cecill.pdf" />
   </licenses>
    <home-page url="http://www.ocera.org"/>

    <hardware processor="i386"/>
    <platform rtlinux="3.1"/>
    <componenttype value="LowLevel"/>

    <keywords>RTLinux Porting</keywords>
  </info>


  <!-- ================================================== Description -->
  <description>
Stand-Alone RTLinux will be a Linux independent implementation of
RTLinux. Stand-Alone RTLinux will be a bootable executive with the
following main features:

a) Low memory overhead. The core systems contains only following
modules: the code of RTLinux, the minimum code needed to boot the
system and basic virtual memory management.

b) Scalability. Users will be able to customize RTLinux funcionalities
to reduce kernel memory usage.

c) Porting will be possible to systems without hardware for virtual
memory support. Therefore, Stand-Alone RTLinux could be ported to a
wider range of architectures.

d) Less TLB and memory cache misses (or none at all, if paging is not
activated) since only real-time applications are being executed.

e) We are not longer limited by the Linux memory manager. Standard
RTLinux memory management relays completely on the Linux so it is not
possible to implement custom virtual memory management algorithms.
Stand-Alone RTLinux has full control of the MMU. Current
implementation provides three different memory schemes:

  1.- Non protected memory. RTLinux executive and application can read
  and write at any memory location.

  2.- Simple memory protection. The application can not write into the
  RTLinux executive memory space, and null pointers are catched.

  3.- Context memory protection: Several applications (each
  application can run one or more threads) are executed in a protected
  memory space. Each aplication can read and write its own data but
  only read system and other applications code and data.

  </description>

</component>

