Thread (9 messages) 9 messages, 5 authors, 7d ago

Re: [PATCH net-next v2 0/2] vsock: receive queue hint for io_uring

From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-09-29 00:31:24
Also in: lkml, netdev

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski [off-list ref]:

On Wed, 23 Sep 2026 19:40:06 +0100 you wrote:
AF_VSOCK stream receives never fill msghdr.msg_inq. io_uring initialises the
hint to -1 and treats that as "unknown", so it cannot set
IORING_CQE_F_SOCK_NONEMPTY, and it speculatively retries a multishot receive
after every completion, including when the queue is already empty.

Patch 1 fills the hint at the common exit of __vsock_connectible_recvmsg(),
reusing vsock_stream_has_data(), the transport callback that SIOCINQ already
uses. Following tcp_inq_hint(), it reports a terminal hint of 1 once the
connection is finished, so the caller still performs the receive that
observes EOF. Patch 2 adds selftest coverage.

[...]
Here is the summary with links:
  - [net-next,v2,1/2] vsock: report pending receive data to io_uring
    https://git.kernel.org/netdev/net-next/c/608e7f84960b
  - [net-next,v2,2/2] vsock/test: cover receive queue hints
    https://git.kernel.org/netdev/net-next/c/c116f78f94a4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help