From: David Carlier <devnexen@gmail.com>
To: netdev@vger.kernel.org
Cc: sgarzare@redhat.com, bobbyeshleman@gmail.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
David Carlier <devnexen@gmail.com>
Subject: [PATCH net-next 0/2] vsock: SO_INQ for stream sockets
Date: Tue, 13 Oct 2026 00:55:22 +0100 [thread overview]
Message-ID: <20261012235524.41468-1-devnexen@gmail.com> (raw)
This is the follow-up announced in the receive queue hint series [1]:
SO_INQ and SCM_INQ for AF_VSOCK stream sockets, as AF_UNIX has.
The value is the one SIOCINQ returns, so on Hyper-V it covers the
current packet only. The flag is per socket, is not inherited by
accepted sockets, and the sockmap receive path does not report it.
Tested over loopback with vsock_test and vsock_uring_test.
[1] https://lore.kernel.org/netdev/20260923184008.153541-1-devnexen@gmail.com/
David Carlier (2):
vsock: support SO_INQ on stream sockets
vsock/test: cover SO_INQ
include/net/af_vsock.h | 1 +
net/vmw_vsock/af_vsock.c | 41 +++++--
tools/testing/vsock/vsock_test.c | 191 +++++++++++++++++++++++++++++++
3 files changed, 224 insertions(+), 9 deletions(-)
base-commit: a4057f51efc2b74ddf46721e83f45e9efb13649d
--
2.55.0
next reply other threads:[~2026-10-12 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 23:55 David Carlier [this message]
2026-10-12 23:55 ` [PATCH net-next 1/2] vsock: support SO_INQ on stream sockets David Carlier
2026-10-13 0:06 ` sashiko-bot
2026-10-12 23:55 ` [PATCH net-next 2/2] vsock/test: cover SO_INQ David Carlier
2026-10-13 0:06 ` sashiko-bot
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=20261012235524.41468-1-devnexen@gmail.com \
--to=devnexen@gmail.com \
--cc=bobbyeshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--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.