vn(4) [debian man page]

MD(4)							   BSD Kernel Interfaces Manual 						     MD(4)

NAME

     md -- memory disk

SYNOPSIS

     device md

DESCRIPTION

     The md driver provides support for four kinds of memory backed virtual disks:

     malloc   Backing store is allocated using malloc(9).  Only one malloc-bucket is used, which means that all md devices with malloc backing
	      must share the malloc-per-bucket-quota.  The exact size of this quota varies, in particular with the amount of RAM in the system.
	      The exact value can be determined with vmstat(8).

     preload  A file loaded by loader(8) with type 'md_image' is used for backing store.  For backwards compatibility the type 'mfs_root' is also
	      recognized.  If the kernel is created with option MD_ROOT the first preloaded image found will become the root file system.

     vnode    A regular file is used as backing store.	This allows for mounting ISO images without the tedious detour over actual physical media.

     swap     Backing store is allocated from buffer memory.  Pages get pushed out to the swap when the system is under memory pressure, otherwise
	      they stay in the operating memory.  Using swap backing is generally preferable over malloc backing.

     For more information, please see mdconfig(8).

EXAMPLES

     To create a kernel with a ramdisk or MD file system, your kernel config needs the following options:

	   options	   MD_ROOT		   # MD is a potential root device
	   options	   MD_ROOT_SIZE=8192	   # 8MB ram disk
	   makeoptions	   MFS_IMAGE=/h/foo/ARM-MD
	   options	   ROOTDEVNAME="ufs:md0"

     The image in /h/foo/ARM-MD will be loaded as the initial image each boot.	To create the image to use, please follow the steps to create a
     file-backed disk found in the mdconfig(8) man page.  Other tools will also create these images, such as NanoBSD.

SEE ALSO

     disklabel(5), disklabel(8), fdisk(8), loader(8), mdconfig(8), mdmfs(8), newfs(8), vmstat(8)

HISTORY

     The md driver first appeared in FreeBSD 4.0 as a cleaner replacement for the MFS functionality previously used in PicoBSD and in the FreeBSD
     installation process.

     The md driver did a hostile takeover of the vn(4) driver in FreeBSD 5.0.

AUTHORS

     The md driver was written by Poul-Henning Kamp <phk@FreeBSD.org>.

BSD
								 October 30, 2007							       BSD

RAM(4)							     Kernel Interfaces Manual							    RAM(4)

NAME

       ram - ram disk driver

SYNOPSIS

       /sys/conf/SYSTEM:
	    NRAM ram_size  # RAM disk size (512-byte blocks)

       major device number(s):
	    block: 3
       minor device encoding:
	    must be zero (0)

DESCRIPTION

       The  ram  pseudo-device provides a very fast extended memory store.  It's use is intended for file systems like /tmp and applications which
       need to access a reasonably large amount of data quickly.

       The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks.  This is also  patchable
       in  the	system	binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
       adb(1)).  This makes it easy to test the effects of different ram disk sizes on system performance.  It's important to note that any  space
       given  to  the ram device is permanently allocated at system boot time.	Dedicating too much memory can adversely affect system performance
       by forcing the system to swap heavily as in a memory poor environment.

       The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer  cache.	It
       may be read and written without regard to physical disk records.  There is no `raw' interface since no speed advantage is gained by such an
       interface with the ram disk.

DISK SUPPORT

       The ram driver does not support pseudo-disks (partitions).  The special files  refer  to  the  entire  `drive'  as  a  single  sequentially
       addressed file.

       A  typical  use	for  the ram disk would be to mount /tmp on it.  Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
       have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.

FILES

       /dev/ram 	   block file
       /dev/MAKEDEV	   script to create special files
       /dev/MAKEDEV.local  script to localize special files

SEE ALSO

       hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)

DIAGNOSTICS

       ram: no space.  There is not enough memory to allocate the space needed by the ram disk.  The ram disk is disabled.  Any attempts to access
       it will return an error.

       ram: not allocated.  No memory was allocated to the ram disk and an attempt was made to open it.  Either not enough memory was available at
       boot time or the kernel variable ram_size was set to zero.

BUGS

       The ram driver is only available under 2.11BSD.

3rd Berkeley Distribution					 Januray 27, 1996							    RAM(4)