Commit abfdb70d authored by Ben Walker's avatar Ben Walker Committed by Jim Harris
Browse files

doc: Fix link titles in userspace.md 



The link titles were the names of the pages, but
those names were then changed.

Change-Id: If24711a941ca42db703e373eea56c6235bed6685
Signed-off-by: default avatarBen Walker <benjamin.walker@intel.com>
Reviewed-on: https://review.gerrithub.io/421550


Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarChangpeng Liu <changpeng.liu@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
parent 495f878a

doc/userspace.md

+9 −9
Original line number Diff line number Diff line
@@ -34,15 +34,15 @@ which is a critical piece of hardware for ensuring memory safety in user space 
drivers. See @ref memory for full details.



Once the device is unbound from the operating system kernel, the operating

system can't use it anymore. For example, if you unbind an NVMe device on

Linux, the devices corresponding to it such as /dev/nvme0n1 will disappear. It

further means that filesystems mounted on the device will also be removed and

kernel filesystems can no longer interact with the device. In fact, the entire

kernel block storage stack is no longer involved. Instead, SPDK provides

re-imagined implementations of most of the layers in a typical operating

system storage stack all as C libraries that can be directly embedded into

your application. This includes a @ref bdev primarily, but also block

allocators and filesystem-like components such as @ref blob and @ref blobfs.

system can't use it anymore. For example, if you unbind an NVMe device on Linux,

the devices corresponding to it such as /dev/nvme0n1 will disappear. It further

means that filesystems mounted on the device will also be removed and kernel

filesystems can no longer interact with the device. In fact, the entire kernel

block storage stack is no longer involved. Instead, SPDK provides re-imagined

implementations of most of the layers in a typical operating system storage

stack all as C libraries that can be directly embedded into your application.

This includes a [block device abstraction layer](@ref bdev) primarily, but

also [block allocators](@ref blob) and [filesystem-like components](@ref blobfs).



User space drivers utilize features in uio or vfio to map the

[PCI BAR](https://en.wikipedia.org/wiki/PCI_configuration_space) for the device