Lines Matching refs:module

11 A block device module is SPDK's equivalent of a device driver in a traditional
12 operating system. The module provides a set of function pointers that are
17 how to write a module.
21 Block device modules are located in subdirectories under module/bdev today. It is not
22 currently possible to place the code for a bdev module elsewhere, but updates
24 module, add a new directory with a single C file and a Makefile. A great
25 starting point is to copy the existing 'null' bdev module.
29 a new bdev module - SPDK_BDEV_MODULE_REGISTER. This macro take as argument a
30 pointer spdk_bdev_module structure that is used to register new bdev module.
32 The spdk_bdev_module structure describes the module properties like
35 will be allocated in each I/O request for use by this module, and a callback
36 that will be called each time a new bdev is registered by another module
42 New bdevs are created within the module by calling spdk_bdev_register(). The
43 module must allocate a struct spdk_bdev, fill it out appropriately, and pass
84 The bdev module must implement these function callbacks.
87 longer needs it. What `destruct` does is up to the module - it may just be
136 block device. Once the I/O request is completed, the module must call
140 Integrating a new bdev module into the build system requires updates to various
145 A User can build their own bdev module and application on top of existing SPDK libraries. The examp…
147 bdev module. Refer to test/external_code/README.md and @ref so_linking for further information.
152 the I/O to other block devices. The canonical example would be a bdev module
156 The module can open the underlying bdevs it wishes to route I/O to using
192 When a virtual bdev module claims an underlying bdev from its `examine_config`
194 module and any others that establish a shared claim. If no claims are taken by