30.07.2013 Views

Development and Implementation of a File System for Gannet Virtual ...

Development and Implementation of a File System for Gannet Virtual ...

Development and Implementation of a File System for Gannet Virtual ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 2.2 Service-based SoC Node (V<strong>and</strong>erbauwhede, 2007a)<br />

The transceiver module within the service node contains transmit <strong>and</strong> receive FIFOs<br />

buffer. Moreover, it allows custom implementation depending on the interconnect<br />

technology type. The service nodes exchange the data in<strong>for</strong>mation as packets. The<br />

transceiver encapsulates the <strong>Gannet</strong> packet on a data link-layer frame. Encapsulated<br />

established by the deployment <strong>of</strong> the communication network on-chip. The way it<br />

encapsulates is very similar with OSI 7 - layer model but the way it works is very<br />

different. As the OSI focuses on quality <strong>of</strong> service <strong>and</strong> error control, on the other<br />

h<strong>and</strong>, network on-chip protocol focuses on the efficiency <strong>and</strong> the effectively the data<br />

is being transferred from one point to another endpoint (Kogel, 2006).<br />

The service reconfigure manager manages the data required <strong>and</strong> produced by the<br />

service core. Service node behaves in a “functional” way as they only interact with<br />

the system through the service manager <strong>and</strong> are stateless (V<strong>and</strong>erbauwhede,<br />

2006a). Thus, every service will produce identical output <strong>for</strong> identical inputs <strong>and</strong> no<br />

side-effects. However, this functional behavior accommodates the enable <strong>of</strong> large-<br />

scale parallelism <strong>and</strong> self-managed distributed processing.<br />

The service manager has a local memory <strong>for</strong> storing the task description <strong>and</strong> data<br />

required by the core. The memory allocation is independent <strong>and</strong> managed by the<br />

service manager. It also acts as a bridge which connects service node with the<br />

service manager in order to exchange the data. There<strong>for</strong>e, service node is task-<br />

agnostic <strong>and</strong> the service manager is unaware <strong>of</strong> the nature <strong>of</strong> the service.<br />

6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!