Subject: SDL-News: non-blocking external DB access from within a process
From: Lars Rawall (lr#telelogic.com)
Date: Tue Aug 24 1999 - 07:25:55 GMT
The originator of this message is responsible for its content.
-----From Lars Rawall <lr#telelogic.com> to sdlnews -----
Dear SDL Community,
I don't know if I qualify as an "Official representative" of Telelogic
but I have been working in Telelogic for more than ten years, mainly
with the SDT operating system and the SDT RTOS integrations.
This is what the SDT OS and RTOS integrations offers.
NOTE! I am in the following using the terminology introduced by Mr. Elie
Cohan from Verilog in his earlier e-mail regarding this subject!
>
The SDT UNIX libarary (Solaris, HP_UX)
1. Mapping of 1 SDL System to 1 UNIX box.
2. Mapping of 1-m SDL Blocks to 1 UNIX box.
3. Mapping of 1-m SDL processes to 1 UNIX box.
NOTE! Internal scheduling within each UNIX box is by default handled by
the native SDT run-time but can also easily be configured to be
scheduled by any external real-time kernel.
The SDT POSIX libary.
1. Mapping of one SDL process instance to one POSIX box(default).
2. Mapping of one SDL process instance-set (all instances of that
process) to one POSIX box. Internal scheduling is handled by the SDT
kernel.
Some words about the general code-generation and OS-integration
philosophy of Telelogic.
The same target code is generated for the SDL System no matter if the
purpose is to generate a Host-simulator, Host-application (the same Host
is used both for developing and running the application) or
Target-application.
An application consists of the following modules:
- Generated code for the application with C-macros generated for SDL
entities.
- A set of header-files descibing the actual mapping of SDL entities for
that type of application. e. g. SDL Set-Timer has one implementation in
a Simulator and an other in a POSIX application.
- A run-time library for that type of application and target.
This philosophy makes it very simple to make a integration to a new
Operating System, it can even be done by a skilled user himself.
Besides the above descibed model for code-generation and RTOS
integration Telelogic can also offer a Highly Optimized
Code-Generator/Operating System, the C-Micro Code Generator and C-Micro
kernel. This Code-Generator is intended for applictions with very
limited memory resources and/or high requirements for performance.
The same Basic mapping can be done in C-Micro:
1. 1 SDL System is mapped to one target entity (stand-alone application
or 1 target task/thread under a target-OS).
Other types of mapping can be done on request and can be highly
optimized and tailored for each particular user.
The user of the C-micro package can easily choose how to optimize the
application with regards to memory consumtions and/or speed. He can also
tailor the size of the run-time kernel by slecting the set of
SDL-constructs he/she wants to use in his/hers appication.
Lars Rawall
Senior Software Engineer
E-mail: lars.rawall#telelogic.se
Tel: +46 40 174758
-- ----------------------------------------------------------Lars Rawall TeleLOGIC AB Senior Software Engineer Kungsgatan 6 E-mail: lars.rawall#telelogic.se Box 4128 Tel: +46 40 174758 S-203 12 MALMO Fax: +46 40 174747 SWEDEN
----------------------------------------------------------
-----End text from Lars Rawall <lr#telelogic.com> to sdlnews ----- Join http://www.sdl-forum.org/Society/members.htm for extra SDL Forum Society benefits For help, email "majordomo#sdl-forum.org" with the body of your email as: help or (iff this does not answer your question) email: owner-sdlnews#sdl-forum.org
This archive was generated by hypermail 2a23 : Sun Jun 16 2013 - 10:41:41 GMT