All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Carlier <devnexen@gmail.com>
Cc: netdev@vger.kernel.org, sgarzare@redhat.com,
	bobbyeshleman@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] vsock: receive queue hint for io_uring
Date: Tue, 29 Sep 2026 00:30:08 +0000	[thread overview]
Message-ID: <179064180888.191583.4189311679177858561.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923184008.153541-1-devnexen@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

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



      parent reply	other threads:[~2026-09-29  0:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 18:40 [PATCH net-next v2 0/2] vsock: receive queue hint for io_uring David Carlier
2026-09-23 18:40 ` [PATCH net-next v2 1/2] vsock: report pending receive data to io_uring David Carlier
2026-09-23 18:46   ` sashiko-bot
2026-09-28 15:00   ` Stefano Garzarella
2026-09-23 18:40 ` [PATCH net-next v2 2/2] vsock/test: cover receive queue hints David Carlier
2026-09-23 18:46   ` sashiko-bot
2026-09-23 19:29   ` Bobby Eshleman
2026-09-28 15:00   ` Stefano Garzarella
2026-09-29  0:30 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179064180888.191583.4189311679177858561.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bobbyeshleman@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devnexen@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.