summaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
authorguest <guest@da047780-0f9f-48de-953f-cd541ee48bbd>2007-10-11 09:37:58 +0000
committerguest <guest@da047780-0f9f-48de-953f-cd541ee48bbd>2007-10-11 09:37:58 +0000
commit25cbc40f659b3890596441e60602e929ec9fd9eb (patch)
treeee22b02b7f1ebcc71c228e7058b8eefbe0ba6dc1 /paper.tex
parenta45546d2bd0375e185833ae5d216f152bd9c3038 (diff)
git-svn-id: svn+ssh://mecka.net/home/svn/rtcorba-paper@8 da047780-0f9f-48de-953f-cd541ee48bbd
Diffstat (limited to 'paper.tex')
-rwxr-xr-xpaper.tex13
1 files changed, 7 insertions, 6 deletions
diff --git a/paper.tex b/paper.tex
index f56561c..9cda653 100755
--- a/paper.tex
+++ b/paper.tex
@@ -126,7 +126,7 @@ CORBA is a Middleware, which allows RPC\footnote{Remote Procedure Call}-based IP
The communication interfaces are defined in IDL\footnote{Interface Definition Language}. The IDL files are compiled into, e.g. c++, java, \dots, code which does the (de)serialization of the datatypes. The interface implementations (CORBA objects) are registered at language specific ORB\footnote{Object Request Broker}s. Each CORBA process owns one ORB, which handles the function requests and returns the calculated values.
\subsection{real-time CORBA}
-\epsin{rtcorbaext}{80}{fig1:f2}{Real-time CORBA}
+\epsin{rtcorbaext}{70}{fig1:f2}{Real-time CORBA}
As shown in figure 2, a real-time capable ORB extends a standard ORB with the following features: locating objects in constant time, preallocation of resources, operating system independent priority handling, priority based scheduling.
\subsection{ACE/TAO}
@@ -141,9 +141,9 @@ The ACE/TAO package is available for all important operating systems. The hole f
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Performance Measurements}
-The measurements were made on embedded systems (Intel Mobile CPU 600 MHz, 512 MB RAM, Intel e100 NIC) with digital I/0 ports. A square-pulse generator is connected with the digital input on the first embedded system (sender) and channel 1 of the oscilloscope. The digital outputs of the embedded systems 2 and 3 (receivers) are connected with channel 2 and 3 of the oscilloscope.
+The measurements were made on embedded systems (Intel Mobile CPU 600 MHz, 512 MB RAM, Intel e100 NIC) with digital I/0 ports. A square-pulse generator is connected with the digital input on the first embedded system (supplier) and channel 1 of the oscilloscope. The digital outputs of the embedded systems 2 and 3 (receivers) are connected with channel 2 and 3 of the oscilloscope.
-\epsin{versuch1}{80}{fig1:f4}{Measurement environment}
+\epsin{versuch4}{80}{fig1:f4}{Measurement environment}
\subsection{RPC}
@@ -153,16 +153,17 @@ Each receiver hosts an object, for writting values to its digital output:
module benchmark{
interface Put{
void Port( in short portNo,
- in short value );
+ in short value,
+ in string data );
};
};
\end{lstlisting}
The \textit{Port} function is called by the \textit{sender} as soon as the state of one of its digital inputs changes. The real end to end latency is meassured with the oscilloscope.
-\epsin{sequenzV1}{80}{fig1:f5}{RPC measurement: sequence diagramm}
+To simulate the transmission of bigger process data images, the parameter \textit{in string data} is read in from a text file, so his length, could be changed after compile time, by editing the text file.
-To simulate the transmission of bigger process data images, a parameter \textit{in string data} was added to the \textit{Port} function. The string was read in from a text file, so his length, could be changed after compile time, by editing the text file.
+\epsin{sequenzV1}{80}{fig1:f5}{RPC measurement: sequence diagramm}
For testing the priorization based scheduling, the following interface was added: