NFU Specification: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
** Two types of data exchange: | ** Two types of data exchange: | ||
** 1. variable exchange | ** 1. variable exchange | ||
***IBP_VAL_[IN,OUT,INOUT] | ***IBP_VAL_[IN, OUT, INOUT] | ||
*** variable/values exchanged directly between nfu client and nfu Op | *** variable/values exchanged directly between nfu client and nfu Op | ||
** 2. IBP Cap handling | ** 2. IBP Cap handling | ||
***IBP_REF_[RD,WR,RDWR] | ***IBP_REF_[RD, WR, RDWR] | ||
***client sends an IBP Cap to server, NFU server returns pointer to mmap of the allocation | ***client sends an IBP Cap to server, NFU server returns pointer to mmap of the allocation | ||
Revision as of 07:41, 1 July 2008
Simple overview:
- NFU server -- "adjacent" to IBP depot.
- NFU Op -- lightweight program, written in C, or Java, depending on server.
- NFU client -- launches nfuOps and exchanges data with it.
- Two types of data exchange:
- 1. variable exchange
- IBP_VAL_[IN, OUT, INOUT]
- variable/values exchanged directly between nfu client and nfu Op
- 2. IBP Cap handling
- IBP_REF_[RD, WR, RDWR]
- client sends an IBP Cap to server, NFU server returns pointer to mmap of the allocation