NFU Specification: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* NFU client -- launches nfuOps and exchanges data with it. | * NFU client -- launches nfuOps and exchanges data with it. | ||
** Two types of data exchange: | ** Two types of data exchange: | ||
**1. variable exchange -- data passed directly between NFU Client and NFU Op | *** 1. variable exchange -- data passed directly between NFU Client and NFU Op | ||
NFU_VAL_IN | NFU_VAL_IN | ||
**2. IBP Cap handling | *** 2. IBP Cap handling | ||
NFU_IBP_RD, client sends an IBP Cap to server, NFU Op does not receive cap, but a pointer to a mmap of the cap. | NFU_IBP_RD, client sends an IBP Cap to server, NFU Op does not receive cap, but a pointer to a mmap of the cap. | ||
Revision as of 07:30, 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 -- data passed directly between NFU Client and NFU Op
- Two types of data exchange:
NFU_VAL_IN
- 2. IBP Cap handling
NFU_IBP_RD, client sends an IBP Cap to server, NFU Op does not receive cap, but a pointer to a mmap of the cap.