From abfdb70d04a0cd478b5f350e39ffa0e45ec6a29b Mon Sep 17 00:00:00 2001 From: Ben Walker Date: Tue, 7 Aug 2018 14:13:39 -0700 Subject: [PATCH] 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 Reviewed-on: https://review.gerrithub.io/421550 Chandler-Test-Pool: SPDK Automated Test System Tested-by: SPDK CI Jenkins Reviewed-by: Changpeng Liu Reviewed-by: Shuhei Matsumoto Reviewed-by: Jim Harris --- doc/userspace.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/userspace.md b/doc/userspace.md index 73a1a0002..54ba1bdfa 100644 --- a/doc/userspace.md +++ b/doc/userspace.md @@ -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