DDE::ORe: Difference between revisions
New page: === Overview === In L4-based systems it is quite common to have multiple applications trying to use the same resource in parallel. One might for instance imagine a setup where multiple L4L... |
No edit summary |
||
| Line 1: | Line 1: | ||
== Overview == | |||
In L4-based systems it is quite common to have multiple applications trying to use the same resource in parallel. One might for instance imagine a setup where multiple L4Linux servers run and try to use the computer's physical network interface. In such cases, the physical resource needs to be multiplexed (or ''virtualized'' in new-age termini). | In L4-based systems it is quite common to have multiple applications trying to use the same resource in parallel. One might for instance imagine a setup where multiple L4Linux servers run and try to use the computer's physical network interface. In such cases, the physical resource needs to be multiplexed (or ''virtualized'' in new-age termini). | ||
ORe (short for '''O'''shkosh '''Re'''surrection) is a best-effort ethernet multiplexer for L4. It provides an abstract send/receive interface for network packets and makes sure that every client gets only those packets it wants to receive. This is achieved by assigning each client a virtual MAC address and filtering packets accordingly. | ORe (short for '''O'''shkosh '''Re'''surrection) is a best-effort ethernet multiplexer for L4. It provides an abstract send/receive interface for network packets and makes sure that every client gets only those packets it wants to receive. This is achieved by assigning each client a virtual MAC address and filtering packets accordingly. | ||
== Using ORe in your application == | |||
=== Prerequisites === | |||
To successfully establish a network connection with ORe, you need the following applications running in addition to the basic L4 stuff you'll be running anyway: | |||
* the ORe server | |||
* L4IO | |||
Optionally you might want to run the Events server so that ORe can obtain termination messages from its clients and can cleanly close connections in that case. | |||
=== ORe and L4Linux | === Connecting to the server === | ||
=== Connection configuration === | |||
=== Sending and receiving packets === | |||
== ORe and L4Linux == | |||
There is an ORe stub driver for L4Linux. | There is an ORe stub driver for L4Linux. | ||
Revision as of 13:53, 3 April 2008
Overview
In L4-based systems it is quite common to have multiple applications trying to use the same resource in parallel. One might for instance imagine a setup where multiple L4Linux servers run and try to use the computer's physical network interface. In such cases, the physical resource needs to be multiplexed (or virtualized in new-age termini).
ORe (short for Oshkosh Resurrection) is a best-effort ethernet multiplexer for L4. It provides an abstract send/receive interface for network packets and makes sure that every client gets only those packets it wants to receive. This is achieved by assigning each client a virtual MAC address and filtering packets accordingly.
Using ORe in your application
Prerequisites
To successfully establish a network connection with ORe, you need the following applications running in addition to the basic L4 stuff you'll be running anyway:
- the ORe server
- L4IO
Optionally you might want to run the Events server so that ORe can obtain termination messages from its clients and can cleanly close connections in that case.
Connecting to the server
Connection configuration
Sending and receiving packets
ORe and L4Linux
There is an ORe stub driver for L4Linux.
