Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

SHMIF(4)		 BSD Kernel Interfaces Manual		      SHMIF(4)

NAME
     shmif — rump shared memory network interface

SYNOPSIS
     #include <rump/rump.h>

     int
     rump_pub_shmif_create(const char *path, int *ifnum);

DESCRIPTION
     The shmif interface uses a memory mapped regular file as a virtual Ether‐
     net bus.  All interfaces connected to the same bus see each others' traf‐
     fic.

     Using a memory mapped regular file as a bus has two implications:

     1.	  The bus identifier is not in flat global namespace.

     2.	  Configuring and using the interface is possible without superuser
	  privileges on the host (normal host file access permissions for the
	  bus hold).

     It is not possible to directly access the host networking facilities from
     a rump virtual kernel using purely shmif.	However, traffic can be routed
     to another rump kernel instance which provides both shmif and virt(4)
     networking.

     An shmif interface can be created in two ways:

     ·	 Programmatically by calling rump_pub_shmif_create().  The bus path‐
	 name is passed in path.  The number of the newly created interface is
	 available after a successful call by dereferencing ifnum.

     ·	 Dynamically at runtime with ifconfig(8) or equivalent using the
	 create command.  In this case the bus path must be configured with
	 ifconfig(8) linkstr before the interface address can be configured.

     Destroying an shmif interface is possible only via ifconfig(8) destroy.

SEE ALSO
     rump(3), virt(4), ifconfig(8)

BSD			       November 17, 2010			   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome