Lines Matching refs:iodev

15 driven I/O. This section covers the RTIO API, queues, executor, iodev,
85 and device on the bus it is embodied in what RTIO calls an iodev.
87 Multiple operations against the same iodev are done in the order provided as
116 job of objects implementing the iodev (IO device) API. This API accepts requests
117 in the form of the iodev submit API call. It is the io devices job to work
120 object, that accepts a never ending queue of I/O like requests. How the iodev
121 does this work is up to the author of the iodev, perhaps the entire queue of
140 to read into is left to the iodev to allocate from a memory pool associated with
144 the iodev. Below is a snippet setting up the RTIO context with a memory pool.
163 with a call to :c:func:`rtio_sqe_prep_read_with_pool`. The iodev requires
166 from the :c:struct:`rtio_iodev_sqe`, the iodev should get the buffer and count
211 There is a small cost to each RTIO context and iodev. This cost could be weighed