1 .\" $NetBSD: rump.3,v 1.5 2009/06/30 15:28:01 pooka Exp $
3 .\" Copyright (c) 2008 Antti Kantee. All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
31 .Nd Runnable Userspace Meta Program kernel
33 rump Library (librump, \-lrump)
36 .In rump/rump_syscalls.h
37 .In rump/rumpvnode_if.h
40 emulates portions of the kernel in order to be able to run kernel code
41 from a userspace application.
42 For most parts kernel code is directly used, but in some cases such as
43 with vm and device drivers a reimplementation suitable for userspace
45 All of the routines in
47 have been compiled in the kernel namespace with
52 includes many kernel routines directly, userspace applications should
53 not attempt to include
55 system headers and call kernel functions directly.
58 routines should be called.
59 In case applications attempt to include
63 tree, collisions will result on other platforms.
65 Three classes of routines are provided by
67 .Bl -tag -width XXX -offset indent
69 These routines have been handwritten for
72 Some are useful purely for
74 while others are merely interfaces to existing kernel routines.
75 An example of the former is
76 .Fn rump_fakeblk_register ,
77 while an example of the latter class is
78 .Fn rump_vfs_unmount .
80 The routines available in this class can be found from the header
83 It is possible to execute certain system calls from
85 However, contrary to real system calls, the kernel is never entered,
86 but the system call backend code compiled into
88 is merely called as a direct function call.
90 The autogenerated list of system calls currently available in
92 can be found from the header
95 To sort out namespace collisions for
98 vnode interface set is provided under a special namespace.
99 The operation is the same as in the kernel, but the interface names
100 begin with the prefix RUMP_VOP.
102 This class of routines is available from the autogenerated header
108 must be initialized by calling
117 .%B Proceedings of AsiaBSDCon 2009
119 .%T Environmental Independence: BSD Kernel TCP/IP in Userspace
125 .%T Kernel Development in Userspace - The Rump Approach
130 .%B Proceedings of the 2009 USENIX Annual Technical Conference
132 .%T Rump File Systems: Kernel Code Reborn
139 .%T Fs-utils: File Systems Access Tools for Userland
146 .An Antti Kantee Aq pooka@iki.fi
149 is highly experimental and may change in header location, library
150 name, API and/or ABI without warning.