The use of name spaces in Plan 9

Pike, Rob; Presotto, Dave; Thompson, Ken; Trickey, Howard; Winterbottom, Phil

doi:10.1145/155848.155861

Cited by 69 publications

(23 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Plan9 introduces a VFS for network streams to reach its design goal that "everything is a file" [23]. Like PipesFS, this replaces sockets with filesystem operations (and both avoid introducing network namespaces [21]), but only PipesFS expands into a generic I/O pipeline through nesting.…”

Section: Related Workmentioning

confidence: 99%

PipesFS

Bruijn

Bos

2008

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

This paper presents PipesFS, an I/O architecture for Linux 2.6 that increases I/O throughput and adds support for heterogeneous parallel processors by (1) collapsing many I/O interfaces onto one: the Unix pipeline, (2) increasing pipe efficiency and (3) exploiting pipeline modularity to spread computation across all available processors.PipesFS extends the pipeline model to kernel I/O and communicates with applications through a Linux virtual filesystem (VFS), where directory nodes represent operations and pipe nodes export live kernel data. Users can thus interact with kernel I/O through existing calls like mkdir, tools like grep, most languages and even shell scripts. To support performance critical tasks, PipesFS improves pipe throughput through copy, context switch and cache miss avoidance. To integrate heterogeneous processors (e.g., the Cell) it transparently moves operations to the most efficient type of core.

show abstract

Section: Related Workmentioning

confidence: 99%

PipesFS

Bruijn

Bos

2008

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

show abstract

“…This is the Plan 9 approach taken to the limit. 11 The environment the user sees is that seen by all the user's applications.…”

Section: Plan B Organizationmentioning

confidence: 99%

Plan B: Using Files instead of Middleware Abstractions

Ballesteros

Soriano

Guardiola

et al. 2007

IEEE Pervasive Comput.

View full text Add to dashboard Cite

resources We provide abstract interfaces, amenable to both users and applications, through (virtual) file trees. Unlike other systems that use files for interfaces (Plan 9, for example), we don't provide pixmaps or other low-level artifacts to support GUIs. We support user interfaces by providing a file tree in which a different file represents each UI element (that is, widget). The same applies to other resources.These files aren't on disk but are provided by resource servers, such as in Plan 9 or Unix's /proc. 3 In addition, we don't propose to intercept file system calls. Rather, we take the Plan 9 approach to the limit and provide all services by implement- Plan B maps abstract interfaces to files and adapts to file tree availability. It is easy to program, offers a general-purpose computing environment, and supports smart spaces without using middleware.The system ensures that the namespace reflects which resources are available and which ones aren't, cleanly removing unavailable resources from the file trees. JULY-SEPTEMBER 2007 PERVASIVE computing 63 Figure 2. A typical Plan B screen, serviced by the Omero UI volume.

show abstract

“…For example, we have combined MLSSH and DEENS with bindings to the user-level tuntap interface to experiment with new distributed naming algorithms in user-space, as well as constructing file systems that export their contents via the DNS (which involved specifying the Plan9 9P protocol [44] using MPL).…”

Section: Configurationmentioning

confidence: 99%

Melange

Madhavapeddy

Deegan

et al. 2007

Proceedings of the 2nd ACM SIGOPS/EuroSys European Conference on Computer Systems 2007

View full text Add to dashboard Cite

Most implementations of critical Internet protocols are written in type-unsafe languages such as C or C++ and are regularly vulnerable to serious security and reliability problems. Type-safe languages eliminate many errors but are not used to due to the perceived performance overheads.We combine two techniques to eliminate this performance penalty in a practical fashion: strong static typing and generative metaprogramming. Static typing eliminates run-time type information by checking safety at compile-time and minimises dynamic checks. Meta-programming uses a single specification to abstract the lowlevel code required to transmit and receive packets.Our domain-specific language, MPL, describes Internet packet protocols and compiles into fast, zero-copy code for both parsing and creating these packets. MPL is designed for implementing quirky Internet protocols ranging from the low-level: Ethernet, IPv4, ICMP and TCP; to the complex application-level: SSH, DNS and BGP; and even file-system protocols such as 9P.We report on fully-featured SSH and DNS servers constructed using MPL and our OCaml framework MELANGE, and measure greater throughput, lower latency, better flexibility and more succinct source code than their C equivalents OpenSSH and BIND. Our quantitative analysis shows that the benefits of MPL-generated code overcomes the additional overheads of automatic garbage collection and dynamic bounds checking. Qualitatively, the flexibility of our approach shows that dramatic optimisations are easily possible.

show abstract

The use of name spaces in Plan 9

Cited by 69 publications

References 1 publication

PipesFS

PipesFS

Plan B: Using Files instead of Middleware Abstractions

Melange

Contact Info

Product

Resources

About