Lines Matching full:server

30 in this document, ``ublk server`` refers to generic ublk userspace
43 assigned by one queue wide unique tag. ublk server assigns unique tag to each
51 done by io_uring, but also the preferred IO handling in ublk server is io_uring
64 ublk requires userspace ublk server to handle real block device logic.
102   Add a ublk char device (``/dev/ublkc*``) which is talked with ublk server
106   for which the info is negotiated with the driver and sent back to the server.
118   After the server prepares userspace resources (such as creating per-queue
126   ublk server will release resources (such as destroying per-queue pthread &
137   that each queue's affinity info is available. The server sends
144   For retrieving device info via ``ublksrv_ctrl_dev_info``. It is the server's
148   Same purpose with ``UBLK_CMD_GET_DEV_INFO``, but ublk server has to
158     If ublk server supports ``UBLK_F_UNPRIVILEGED_DEV``:
160     ublk server should send ``UBLK_CMD_GET_DEV_INFO2``, given anytime
166     If ublk server doesn't support ``UBLK_F_UNPRIVILEGED_DEV``:
173     If ublk server supports ``UBLK_F_UNPRIVILEGED_DEV``:
179     If ublk server doesn't support ``UBLK_F_UNPRIVILEGED_DEV``:
205   With ``UBLK_F_USER_RECOVERY`` set, after one ubq_daemon(ublk server's io
207   recovery stage and ublk device ID is kept. It is ublk server's
213   server's io handler) is dying, contrary to ``UBLK_F_USER_RECOVERY``,
225 be provided in these commands' payload from ublk server. With this way,
232 ublk server needs to create per-queue IO pthread & io_uring for handling IO
242 exporting IO info to the server; such as IO offset, length, OP/flags and
252   Sent from the server IO pthread for fetching future incoming IO requests
253   destined to ``/dev/ublkb*``. This command is sent only once from the server
261   or ``UBLK_IO_COMMIT_AND_FETCH_REQ)`` is completed, so the server gets
264   After the server handles the IO, its result is committed back to the
274   issued to ublk server without data copy. Then, IO backend of ublk server
283   should not enable UBLK_F_NEED_GET_DATA. ublk server pre-allocates IO
290 - data copy between ublk server IO buffer and ublk block IO request
292   The driver needs to copy the block IO request pages into the server buffer
293   (pages) first for WRITE before notifying the server of the coming IO, so
294   that the server can handle WRITE request.
296   When the server handles READ request and sends
297   ``UBLK_IO_COMMIT_AND_FETCH_REQ`` to the server, ublkdrv needs to copy
298   the server buffer (pages) read to the IO request pages.