Skip to content

Add support for IORING_CQE_F_SOCK_FULL

Jens Axboe io-uring 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2io_uring/poll: flag request with REQ_F_POLL_TRIGGERED if it went through pollinclude/linux/io_uring_types.h io_uring/poll.c+4 -00 replies
2/2io_uring/net: add IORING_CQE_F_SOCK_FULL if a send needed to poll arminclude/uapi/linux/io_uring.h io_uring/net.c+17 -60 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCHSET 0/2] Add support for IORING_CQE_F_SOCK_FULL

Hi,

It can be useful for userspace to know if a send request had to go through poll to complete, as that generally means that the socket was out of space. On the send side, this is pretty trivial to support - we just need to check if the request needed to go through poll to complete.

This reuses the IORING_CQE_F_SOCK_NONEMPTY flag value, which is only valid for recv operations. As IORING_CQE_F_SOCK_FULL only applies on sends, there's no need for separate values for this flag.

Based on an earlier patchset, which utilized REQ_F_POLL_ARMED instead and handled patch 1 a bit differently.

 include/linux/io_uring_types.h |  3 +++
 include/uapi/linux/io_uring.h  |  4 ++++
 io_uring/net.c                 | 19 +++++++++++++------
 io_uring/poll.c                |  1 +
 4 files changed, 21 insertions(+), 6 deletions(-)
Signature · 1 line
Jens Axboe