nvd(4) [freebsd man page]

NVD(4)							   BSD Kernel Interfaces Manual 						    NVD(4)

NAME

     nvd -- NVM Express disk driver

SYNOPSIS

     To compile this driver into your kernel, place the following lines in your kernel configuration file:

	   device nvme
	   device nvd

     Or, to load the driver as a module at boot, place the following lines in loader.conf(5):

	   nvme_load="YES"
	   nvd_load="YES"

DESCRIPTION

     The nvd driver exposes NVM Express (NVMe) namespaces as disks to the kernel disk storage API.  It depends on the nvme(4) driver for notifica-
     tion of existing NVMe namespaces and submission of NVM I/O commands.

     Device nodes from the nvd driver will have the format /dev/nvdX and are GEOM(4) disks which can be partitioned by geom(8).  Note that device
     nodes from the nvme(4) driver are not GEOM(4) disks and cannot be partitioned.

SEE ALSO

     GEOM(4), nvme(4), geom(8), nvmecontrol(8), disk(9)

HISTORY

     The nvd driver first appeared in FreeBSD 9.2.

AUTHORS

     The nvd driver was developed by Intel and originally written by Jim Harris <jimharris@FreeBSD.org>, with contributions from Joe Golio at EMC.

     This man page was written by Jim Harris <jimharris@FreeBSD.org>.

BSD
								  March 18, 2014							       BSD

GEOM_UZIP(4)                                               BSD Kernel Interfaces Manual                                               GEOM_UZIP(4)

NAME

     geom_uzip -- GEOM based compressed disk images

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

           options GEOM_UZIP

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

           geom_uzip_load="YES"

DESCRIPTION

     The geom_uzip framework provides support for compressed read only disk images.  This allows significant storage savings at the expense of a
     little CPU time on each read.  Data written in the GEOM label area allows geom_uzip to detect compressed images which have been created with
     mkuzip(8) and presented to the kernel as a logical disk device via md(4).  geom_uzip creates a unique md#.uzip device for each image.

     The geom_uzip device is subsequently used by the FreeBSD kernel to access the disk images.  The geom_uzip driver does not allow write opera-
     tions to the underlying disk image.  To check which md(4) devices match a given geom_uzip device:

           # geom uzip list
           Geom name: md1.uzip
           Providers:
           1. Name: md1.uzip
              Mediasize: 22003712 (21M)
              Sectorsize: 512
              Mode: r1w0e1
           Consumers:
           1. Name: md1
              Mediasize: 9563648 (9.1M)
              Sectorsize: 512
              Mode: r1w0e1

SEE ALSO

     GEOM(4), md(4), geom(8), mkuzip(8)

AUTHORS

     The geom_uzip driver was written by Max Khon <fjoe@FreeBSD.org>.  This manual page was written by Ceri Davies <ceri@FreeBSD.org>.

BSD                                                               October 9, 2006                                                              BSD