From: Stefano Garzarella <sgarzare@redhat.com>
To: Jia Jia <physicalmtea@gmail.com>
Cc: stefanha@redhat.com, mst@redhat.com, jasowangio@gmail.com,
eperezma@redhat.com, xuanzhuo@linux.alibaba.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bobbyeshleman@gmail.com
Subject: Re: [PATCH net-next v4 4/4] vsock/virtio: defer RX notifications until batch unlock
Date: Mon, 19 Oct 2026 16:11:57 +0200 [thread overview]
Message-ID: <atYlFHcjGMFxHCuM@sgarzare-redhat> (raw)
In-Reply-To: <CAJwVaMLmMf1iyWmoZMAJuS2551DsSWSkcRsUVz3M5xi9AXWsWg@mail.gmail.com>
On Sun, Oct 18, 2026 at 12:55:35PM +0800, Jia Jia wrote:
>>
>> On Wed, Oct 14, 2026 at 07:56:40PM +0800, Jia Jia wrote:
>> >An RX batch can make a socket readable while the worker still holds its
>> >socket lock. Waking a blocking reader then only moves it to waiting for
>> >the same lock.
>> >
>> >Record the existing low-watermark condition and notify once after
>> >release_sock(). Move the coalesced write-space notification after the
>> >unlock as well, since both callbacks wake sk_sleep(sk). Deliver
>> >write-space before data-ready and keep the lookup reference until both
>> >callbacks complete.
>> >
>> >As with write-space, save the initial sk_data_ready callback and batch only
>> >while both saved callbacks remain installed. Sockets with replaced
>> >callbacks retain their per-packet behavior.
>> >
>> >The existing psock-marker check also covers a concurrent sockmap attach:
>> >at most the already admitted packet completes on the native path, and the
>> >next packet ends the batch.
>> >
>> >Signed-off-by: Jia Jia <physicalmtea@gmail.com>
>> >---
>> > include/linux/virtio_vsock.h | 1 +
>> > include/net/af_vsock.h | 5 ++--
>> > net/vmw_vsock/af_vsock.c | 1 +
>> > net/vmw_vsock/virtio_transport_common.c | 35 ++++++++++++++++++-------
>> > 4 files changed, 31 insertions(+), 11 deletions(-)
>> >
>> >diff --git a/include/linux/virtio_vsock.h b/include/linux/virtio_vsock.h
>> >index bf077ee0ded88..f1396ca3ad9b5 100644
>> >--- a/include/linux/virtio_vsock.h
>> >+++ b/include/linux/virtio_vsock.h
>> >@@ -288,6 +288,7 @@ struct virtio_transport_rx_batch {
>> > unsigned int pkts;
>> > size_t bytes;
>> > bool write_space_pending;
>> >+ bool data_ready_pending;
>> > };
>> >
>> > void virtio_transport_recv_pkt_batch(struct virtio_transport *t,
>> >diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
>> >index 9a40960d10cbe..78bab5820f528 100644
>> >--- a/include/net/af_vsock.h
>> >+++ b/include/net/af_vsock.h
>> >@@ -64,9 +64,10 @@ struct vsock_sock {
>> > bool sent_request;
>> > bool ignore_connecting_rst;
>> > /*
>> >- * Initial callback, used to identify replacements and deliver deferred
>> >- * write-space notifications.
>> >+ * Initial callbacks, used to identify replacements and deliver deferred
>> >+ * notifications.
>> > */
>> >+ void (*default_data_ready)(struct sock *sk);
>> > void (*default_write_space)(struct sock *sk);
>> >
>> > /* Protected by lock_sock(sk) */
>> >diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
>> >index fe7f49da6c4bc..f40659ec29df0 100644
>> >--- a/net/vmw_vsock/af_vsock.c
>> >+++ b/net/vmw_vsock/af_vsock.c
>> >@@ -958,6 +958,7 @@ static struct sock *__vsock_create(struct net *net,
>> > sk->sk_type = type;
>> >
>> > vsk = vsock_sk(sk);
>> >+ vsk->default_data_ready = sk->sk_data_ready;
>> > vsk->default_write_space = sk->sk_write_space;
>> > vsock_addr_init(&vsk->local_addr, VMADDR_CID_ANY, VMADDR_PORT_ANY);
>> > vsock_addr_init(&vsk->remote_addr, VMADDR_CID_ANY, VMADDR_PORT_ANY);
>> >diff --git a/net/vmw_vsock/virtio_transport_common.c b/net/vmw_vsock/virtio_transport_common.c
>> >index f4b5f0230493e..8b62b789b71c5 100644
>> >--- a/net/vmw_vsock/virtio_transport_common.c
>> >+++ b/net/vmw_vsock/virtio_transport_common.c
>> >@@ -1588,7 +1588,8 @@ virtio_transport_recv_enqueue(struct vsock_sock *vsk,
>> >
>> > static int
>> > virtio_transport_recv_connected(struct sock *sk,
>> >- struct sk_buff *skb)
>> >+ struct sk_buff *skb,
>> >+ bool *data_ready_pending)
>> > {
>> > struct virtio_vsock_hdr *hdr = virtio_vsock_hdr(skb);
>> > struct vsock_sock *vsk = vsock_sk(sk);
>> >@@ -1607,7 +1608,13 @@ virtio_transport_recv_connected(struct sock *sk,
>> > vsock_remove_sock(vsk);
>> > break;
>> > }
>> >- vsock_data_ready(sk);
>> >+ if (!data_ready_pending) {
>> >+ vsock_data_ready(sk);
>> >+ } else if (!*data_ready_pending &&
>> >+ (vsock_stream_has_data(vsk) >= sk->sk_rcvlowat ||
>> >+ sock_flag(sk, SOCK_DONE))) {
>> >+ *data_ready_pending = true;
>> >+ }
>> > return err;
>> > case VIRTIO_VSOCK_OP_CREDIT_REQUEST:
>> > virtio_transport_send_credit_update(vsk);
>> >@@ -1820,6 +1827,7 @@ virtio_transport_recv_pkt_batchable(struct virtio_transport *t,
>> > return sk->sk_state == TCP_ESTABLISHED &&
>> > sk->sk_type == SOCK_STREAM &&
>> > READ_ONCE(sk->sk_prot) == sk->sk_prot_creator &&
>> >+ READ_ONCE(sk->sk_data_ready) == vsk->default_data_ready &&
>> > READ_ONCE(sk->sk_write_space) == vsk->default_write_space &&
>> > !sock_flag(sk, SOCK_DONE) &&
>> > vsk->transport == &t->transport &&
>> >@@ -1830,8 +1838,9 @@ virtio_transport_recv_pkt_batchable(struct virtio_transport *t,
>> > /*
>> > * The caller holds sk's socket lock. Set @batchable if the socket can remain
>> > * locked for another ordinary STREAM/RW packet. When @batch is non-NULL,
>> >- * record a default write-space notification for batch finish instead of
>> >- * delivering it immediately. Return true if the caller must free @skb.
>> >+ * record default write-space and data-ready notifications for batch finish
>> >+ * instead of delivering them immediately. Return true if the caller must
>> >+ * free @skb.
>> > */
>> > static bool
>> > virtio_transport_recv_pkt_locked(struct virtio_transport *t,
>> >@@ -1883,7 +1892,9 @@ virtio_transport_recv_pkt_locked(struct virtio_transport *t,
>> > kfree_skb(skb);
>> > break;
>> > case TCP_ESTABLISHED:
>> >- virtio_transport_recv_connected(sk, skb);
>> >+ virtio_transport_recv_connected(sk, skb,
>> >+ batch ?
>> >+ &batch->data_ready_pending : NULL);
>> > break;
>> > case TCP_CLOSING:
>> > virtio_transport_recv_disconnecting(sk, skb);
>> >@@ -1957,27 +1968,33 @@ EXPORT_SYMBOL_GPL(virtio_transport_recv_pkt);
>> > /*
>> > * Finish the RX batch.
>> > * For a non-empty batch, the caller holds the socket lock acquired with
>> >- * lock_sock(). Deliver any deferred write-space notification while the lock
>> >- * is held, then release the lock and the batch's lookup reference.
>> >- * An empty batch is a no-op.
>> >+ * lock_sock(). Release the lock, deliver any deferred write-space and
>> >+ * data-ready notifications in that order, then drop the batch's lookup
>> >+ * reference. An empty batch is a no-op.
>> > */
>> > void virtio_transport_rx_batch_finish(struct virtio_transport_rx_batch *batch)
>> > {
>> > bool write_space_pending = batch->write_space_pending;
>> >+ bool data_ready_pending = batch->data_ready_pending;
>> > struct sock *sk = batch->sk;
>> >
>> > batch->sk = NULL;
>> > batch->pkts = 0;
>> > batch->bytes = 0;
>> > batch->write_space_pending = false;
>> >+ batch->data_ready_pending = false;
>> >
>> > if (!sk)
>> > return;
>> >
>> >+ release_sock(sk);
>> >+
>>
>> Why in the previous patch we release the socket after calling
>> default_write_space() and now we are moving before?
>>
>
>My intention was to keep the two behavioral changes separately
>testable. Patch 3 is a complete intermediate state: it coalesces
>repeated sk_write_space()
>notifications while preserving the existing under-lock callback
>context. Patch 4 then adds data-ready coalescing and moves both
>deferred notifications
>after release_sock(). Patch 4 therefore builds on Patch 3 rather than fixing it.
Okay, I see, makes sense, please make it clear in the commit
description.
Thanks,
Stefano
>
>> > if (write_space_pending)
>> > vsock_sk(sk)->default_write_space(sk);
>> >
>> >- release_sock(sk);
>> >+ if (data_ready_pending)
>> >+ vsock_sk(sk)->default_data_ready(sk);
>> >+
>> > sock_put(sk);
>> > }
>> > EXPORT_SYMBOL_GPL(virtio_transport_rx_batch_finish);
>> >--
>> >2.53.0
>> >
>>
>
prev parent reply other threads:[~2026-10-19 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 11:56 [PATCH net-next v4 0/4] vsock/virtio: reduce RX per-packet socket overhead Jia Jia
2026-10-14 11:56 ` [PATCH net-next v4 1/4] vsock/virtio: split socket lookup from locked RX processing Jia Jia
2026-10-16 13:47 ` Stefano Garzarella
2026-10-16 14:31 ` Bobby Eshleman
2026-10-18 4:42 ` Jia Jia
2026-10-14 11:56 ` [PATCH net-next v4 2/4] vsock/virtio: amortize RX socket locking for stream packets Jia Jia
2026-10-16 14:33 ` Stefano Garzarella
2026-10-18 4:52 ` Jia Jia
2026-10-19 14:05 ` Stefano Garzarella
2026-10-14 11:56 ` [PATCH net-next v4 3/4] vsock/virtio: coalesce RX write-space notifications in lock batches Jia Jia
2026-10-16 14:07 ` Bobby Eshleman
2026-10-18 4:58 ` Jia Jia
2026-10-16 14:40 ` Stefano Garzarella
2026-10-18 4:54 ` Jia Jia
2026-10-19 14:10 ` Stefano Garzarella
2026-10-14 11:56 ` [PATCH net-next v4 4/4] vsock/virtio: defer RX notifications until batch unlock Jia Jia
2026-10-16 14:42 ` Stefano Garzarella
2026-10-18 4:55 ` Jia Jia
2026-10-19 14:11 ` Stefano Garzarella [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=atYlFHcjGMFxHCuM@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=bobbyeshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=physicalmtea@gmail.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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®