History

io_uring/net: Allow to do vectorized send

At the moment you have to use sendmsg for vectorized send. While this works it's suboptimal as it also means you need to allocate a struct msghdr that needs to be kept alive until a submission happens. We can remove this limitation by just allowing to use send directly.

Norman Maurer committed 1 year ago

Commit 6f025271 parent 4b290aa2 files · +11 −2Browse files

Showing the changes to include/uapi/linux (1 of 2 files). Show all

Unified · Split

include/uapi/linux/io_uring.h+4−0
@@ -392,12 +392,16 @@ enum io_uring_op { · 391 unmodified lines
392392 * the starting buffer ID in cqe->flags as per
393393 * usual for provided buffer usage. The buffers
394394 * will be contiguous from the starting buffer ID.
395+ *
396+ * IORING_SEND_VECTORIZED If set, SEND[_ZC] will take a pointer to a io_vec
397+ * to allow vectorized send operations.
395398 */
396399 #define IORING_RECVSEND_POLL_FIRST (1U << 0)
397400 #define IORING_RECV_MULTISHOT (1U << 1)
398401 #define IORING_RECVSEND_FIXED_BUF (1U << 2)
399402 #define IORING_SEND_ZC_REPORT_USAGE (1U << 3)
400403 #define IORING_RECVSEND_BUNDLE (1U << 4)
404+#define IORING_SEND_VECTORIZED (1U << 5)
401405
402406 /*
403407 * cqe.res for IORING_CQE_F_NOTIF if