Skip to content

Latest commit

 

History

History
38 lines (28 loc) · 1.42 KB

non.md

File metadata and controls

38 lines (28 loc) · 1.42 KB
Raw

Network of Namespaces (NoN)

what

Namespaces can be seen as internet nodes. This is a way to implement the idea of Internet of Threads.

why

Because through Network of Namespaces it is possible to implement the idea of Internet of Threads in a way which preserves the backwards compatibility with all the server and client software running on Linux.

The networking stacks used by NoN are instances of the networking services provided by the kernel. NoN has a performance comparable to the native networking support.

how

vdens create User Namespaces connected to VDE plugs. This means that vdens namespaces can use all the plug-ins compatible with the vdeplug4 project.

Examples:

  • vdens vde:///var/run/mynet: NoN connected to a vde switch
  • vdens slirp://: NoN connected to slirp
  • vdens vxvde://239.0.0.1: NoN connected to a local Area Cloud
  • vdens -m vxvde://239.0.0.1 vxvde://239.0.0.2: NoN as a gateway between two local Area Clouds

where

The idea is implemented in vdens.

references:

  • R. Davoli, VXVDEX: Internet of threads and networks of namespaces, 2017 IEEE International Conference on Communications (ICC), Paris, 2017, pp. 1-6.
  • Presentation at LinuxLab 2017