AMP: experiences with building an exokernel-based platform for active networking

Serviter: A service-oriented programmable network platform for shared infrastructure

“…This model represents the hardware architecture and capabilities required by Serviter components. Our attempts to choose a HBA based on models from manufactures or research projects found the models either did not facilitate sufficient programmability [9], were platform specific [10][11][12], or did not separate the forwarding and control planes [13][14][15][16]. Therefore, we studied trends in router hardware development and produced an abstraction tailored to future router platforms, but general and flexible enough to permit its adaptation onto some current platforms for testing and demonstration purposes.…”

“…Explicit allocation, which is employed in [12,[14][15][16], refers to a model where resources are allocated to a domain (a collection/path of services) according to a predetermined fixed specification. Systems adopting this model require the specification of resource requirements for each domain when executed on each different type of control plane platform.…”

Distributed workflow management for large-scale grid environments

“…Other active networks frameworks are either bundled deeper with the operating system kernel, e.g., Silk [12], or as loose as Janos, e.g., AMP [6], which runs on top of various operating system.…”

Snow on Silk: A NodeOS in the Linux Kernel

“…Such a single address space system cannot guarantee separation between concurrent EEs. Finally, AMP [8] is layered on top of the MIT exokernel [13], and the NodeOS was implemented within a user space OS library, with its own memory and thread management. Although this design comparatively taxed system performance, its primary focus on security contributed several issues to the ongoing design of the NodeOS interface.…”

“…Previous NodeOS systems Bowman [15], Janos [26], AMP [8] and Scout [19], only partially addressed these goals. Our central contribution lies in the design and implementation of such a system, a NodeOS within the Linux kernel, and the demonstration of how we maintain performance comparable to Linux for routing on behalf of active applications.…”