From: Stefano Garzarella <sgarzare@redhat.com>
To: David Carlier <devnexen@gmail.com>
Cc: netdev@vger.kernel.org, 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 2/2] vsock/test: cover receive queue hints
Date: Mon, 28 Sep 2026 17:00:47 +0200 [thread overview]
Message-ID: <arqBCldsgfzf1nUW@sgarzare-redhat> (raw)
In-Reply-To: <20260923184008.153541-3-devnexen@gmail.com>
On Wed, Sep 23, 2026 at 07:40:08PM +0100, David Carlier wrote:
> Add io_uring receive tests checking IORING_CQE_F_SOCK_NONEMPTY across a
> partial receive, draining while the peer stays connected, EOF, a
> nonblocking receive on an empty queue, a zero-length request, and a
> multishot receive with provided buffers.
>
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> tools/testing/vsock/util.c | 9 +
> tools/testing/vsock/util.h | 1 +
> tools/testing/vsock/vsock_uring_test.c | 391 +++++++++++++++++++++++++
> 3 files changed, 401 insertions(+)
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
next prev parent reply other threads:[~2026-09-28 15:01 UTC|newest]
Thread overview: 7+ 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-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 19:29 ` Bobby Eshleman
2026-09-28 15:00 ` Stefano Garzarella [this message]
2026-09-29 0:30 ` [PATCH net-next v2 0/2] vsock: receive queue hint for io_uring patchwork-bot+netdevbpf
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=arqBCldsgfzf1nUW@sgarzare-redhat \
--to=sgarzare@redhat.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®