![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Open Space Discussion - Multiple address space support, framework extensions Topic Summary: Created On: 13-Jun-2006 19:32 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Discussion Topic: Multiple address space support, framework extensions (VxWorks)
Leader Name: Andreas Anderegg Attendees: Clemens Maas Georg Heinrich Doron Green Peter Schmittinger Matthias ReiBmann Jens Laudien Holger Dethlefs Martin Stockl Eike Römer Name Missing Stenio Lingaya Session Notes: The main idea of using multiple address spaces is to protect each address space from being manipulated by another. There are different issues Rhapsody customers would like to be implemented to support this mechanism. (background: this topic refers to having multiple processes, each in its address space, like used in Integrity and VxWorks) It is important to not allow direct access to another address space, the main idea is to protect the address spaces from manipulation by each other. This makes a controller for interprocess communication necessary. Roadmap: Support for multiple address spaces will be implemented in a special branch of the Integrity OXF. For each object you can set an option to have it in another address space. Sending events will still be possible by naming the receiving object?s name and the event. Internal communication can be done like always, when communicating with another address space, you use the receiver?s name for addressing. Rhapsody 7.0 MR1 will support multiple address spaces with Integrity. Integrity Implementation: Integrity integrates parts for different address spaces. Its shared memory is used to manage integration, a routing table is implemented. Integrity will be supported for multiple address spaces in Rhapsody 7.0 MR1. RTPs / interprocess communication will not be supported in that version. VxWorks Implementation: VxWorks worked with only tasks, but recently they have added process / RTP support. You can select, which of your objects should run in the one Kernel Space or in the Users Spaces. A solution needs to be found to let processes and threads run mixed up in VxWorks. Animation: Also Rhapsody would need an extension to support animation and debugging of different components/executables that run in different address spaces and communicate with each other at once. A Workaround is to build a kind of super-binary just for animation which internally maps the different processes and address spaces to threads and puts all together in one executable. Initially, no support for animation of multiple processes in a single Rhapsody will be implemented. Alternative Implementation: Mark Richardson has a different approach available as a prototype solution, which works with RTP and VxWorks. It uses an alternative OXF. It allows use of sockets like shared memory for communication and RTPs. A total different topic is to manage when near and far memory on small targets is used. It allows you to tune your system and controls the sizes of created opcodes. This was not the topic of this discussion. Please feel free to dicuss this further... |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.