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: Ben 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: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
Ben Walker 2018-08-07 14:13:39 -07:00 committed by Jim Harris
parent 495f878a52
commit abfdb70d04

View File

@ -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. drivers. See @ref memory for full details.
Once the device is unbound from the operating system kernel, the operating 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 system can't use it anymore. For example, if you unbind an NVMe device on Linux,
Linux, the devices corresponding to it such as /dev/nvme0n1 will disappear. It the devices corresponding to it such as /dev/nvme0n1 will disappear. It further
further means that filesystems mounted on the device will also be removed and means that filesystems mounted on the device will also be removed and kernel
kernel filesystems can no longer interact with the device. In fact, the entire filesystems can no longer interact with the device. In fact, the entire kernel
kernel block storage stack is no longer involved. Instead, SPDK provides block storage stack is no longer involved. Instead, SPDK provides re-imagined
re-imagined implementations of most of the layers in a typical operating implementations of most of the layers in a typical operating system storage
system storage stack all as C libraries that can be directly embedded into stack all as C libraries that can be directly embedded into your application.
your application. This includes a @ref bdev primarily, but also block This includes a [block device abstraction layer](@ref bdev) primarily, but
allocators and filesystem-like components such as @ref blob and @ref blobfs. also [block allocators](@ref blob) and [filesystem-like components](@ref blobfs).
User space drivers utilize features in uio or vfio to map the 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 [PCI BAR](https://en.wikipedia.org/wiki/PCI_configuration_space) for the device