Lines Matching refs:a

6 important to understand what that means at a technical level. First and
7 foremost, a _driver_ is software that directly controls a particular device
8 attached to a computer. Second, operating systems segregate the system's
18 In order for SPDK to take control of a device, it must first instruct the
21 [writing to a file in sysfs](https://lwn.net/Articles/143397/).
27 system that the device has a driver bound to it so it won't automatically try
33 which is a critical piece of hardware for ensuring memory safety in user space
42 implementations of most of the layers in a typical operating system storage
44 This includes a [block device abstraction layer](@ref bdev) primarily, but
59 are a number of reasons for doing this: 1) practically speaking, routing an
60 interrupt to a handler in a user space process just isn't feasible for most
63 universally asynchronous and allow the user to provide a callback on
64 completion. The callback is called in response to the user calling a function
66 memory needs to be read (no MMIO) to check a queue pair for a bit flip and
81 to 1:1 as possible), and then when a request is submitted they look up the
83 running on. Often, they'll need to either acquire a lock around the queue or
85 running on the same core, which can be expensive. This is a large improvement
86 from older hardware interfaces that only had a single queue or no queue at
89 A user space driver, on the other hand, is embedded into a single application.
93 that a hardware queue is only ever accessed from one thread at a time. In