From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Bobby Eshleman <bobby.eshleman@bytedance.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@sberdevices.ru, oxffffaa@gmail.com
Subject: Re: [PATCH net-next v8 3/4] virtio/vsock: fix logic which reduces credit update messages
Date: Tue, 12 Dec 2023 10:54:16 -0500 [thread overview]
Message-ID: <20231212105322-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231211211658.2904268-4-avkrasnov@salutedevices.com>
On Tue, Dec 12, 2023 at 12:16:57AM +0300, Arseniy Krasnov wrote:
> Add one more condition for sending credit update during dequeue from
> stream socket: when number of bytes in the rx queue is smaller than
> SO_RCVLOWAT value of the socket. This is actual for non-default value
> of SO_RCVLOWAT (e.g. not 1) - idea is to "kick" peer to continue data
> transmission, because we need at least SO_RCVLOWAT bytes in our rx
> queue to wake up user for reading data (in corner case it is also
> possible to stuck both tx and rx sides, this is why 'Fixes' is used).
I don't get what does "to stuck both tx and rx sides" mean.
Besides being agrammatical, is there a way to do this without
playing with SO_RCVLOWAT?
>
> Fixes: b89d882dc9fc ("vsock/virtio: reduce credit update messages")
> Signed-off-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
> ---
> Changelog:
> v6 -> v7:
> * Handle wrap of 'fwd_cnt'.
> * Do to send credit update when 'fwd_cnt' == 'last_fwd_cnt'.
> v7 -> v8:
> * Remove unneeded/wrong handling of wrap for 'fwd_cnt'.
>
> net/vmw_vsock/virtio_transport_common.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/net/vmw_vsock/virtio_transport_common.c b/net/vmw_vsock/virtio_transport_common.c
> index e137d740804e..8572f94bba88 100644
> --- a/net/vmw_vsock/virtio_transport_common.c
> +++ b/net/vmw_vsock/virtio_transport_common.c
> @@ -558,6 +558,8 @@ virtio_transport_stream_do_dequeue(struct vsock_sock *vsk,
> struct virtio_vsock_sock *vvs = vsk->trans;
> size_t bytes, total = 0;
> struct sk_buff *skb;
> + u32 fwd_cnt_delta;
> + bool low_rx_bytes;
> int err = -EFAULT;
> u32 free_space;
>
> @@ -601,7 +603,10 @@ virtio_transport_stream_do_dequeue(struct vsock_sock *vsk,
> }
> }
>
> - free_space = vvs->buf_alloc - (vvs->fwd_cnt - vvs->last_fwd_cnt);
> + fwd_cnt_delta = vvs->fwd_cnt - vvs->last_fwd_cnt;
> + free_space = vvs->buf_alloc - fwd_cnt_delta;
> + low_rx_bytes = (vvs->rx_bytes <
> + sock_rcvlowat(sk_vsock(vsk), 0, INT_MAX));
>
> spin_unlock_bh(&vvs->rx_lock);
>
> @@ -611,9 +616,11 @@ virtio_transport_stream_do_dequeue(struct vsock_sock *vsk,
> * too high causes extra messages. Too low causes transmitter
> * stalls. As stalls are in theory more expensive than extra
> * messages, we set the limit to a high value. TODO: experiment
> - * with different values.
> + * with different values. Also send credit update message when
> + * number of bytes in rx queue is not enough to wake up reader.
> */
> - if (free_space < VIRTIO_VSOCK_MAX_PKT_BUF_SIZE)
> + if (fwd_cnt_delta &&
> + (free_space < VIRTIO_VSOCK_MAX_PKT_BUF_SIZE || low_rx_bytes))
> virtio_transport_send_credit_update(vsk);
>
> return total;
> --
> 2.25.1
next prev parent reply other threads:[~2023-12-12 15:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 21:16 [PATCH net-next v8 0/4] send credit update during setting SO_RCVLOWAT Arseniy Krasnov
2023-12-11 21:16 ` [PATCH net-next v8 1/4] vsock: update SO_RCVLOWAT setting callback Arseniy Krasnov
2023-12-11 21:16 ` [PATCH net-next v8 2/4] virtio/vsock: send credit update during setting SO_RCVLOWAT Arseniy Krasnov
2023-12-11 21:16 ` [PATCH net-next v8 3/4] virtio/vsock: fix logic which reduces credit update messages Arseniy Krasnov
2023-12-12 8:56 ` Stefano Garzarella
2023-12-12 15:54 ` Michael S. Tsirkin [this message]
2023-12-12 15:50 ` Arseniy Krasnov
2023-12-12 16:11 ` Michael S. Tsirkin
2023-12-12 17:41 ` Arseniy Krasnov
2023-12-11 21:16 ` [PATCH net-next v8 4/4] vsock/test: two tests to check credit update logic Arseniy Krasnov
2023-12-12 15:54 ` [PATCH net-next v8 0/4] send credit update during setting SO_RCVLOWAT Michael S. Tsirkin
2023-12-12 15:59 ` Arseniy Krasnov
2023-12-12 16:12 ` Michael S. Tsirkin
2023-12-12 17:43 ` Arseniy Krasnov
2023-12-13 8:43 ` Stefano Garzarella
2023-12-13 9:08 ` Arseniy Krasnov
2023-12-13 9:41 ` Stefano Garzarella
2023-12-13 10:08 ` Arseniy Krasnov
2023-12-13 15:05 ` Michael S. Tsirkin
2023-12-13 15:13 ` Michael S. Tsirkin
2023-12-13 17:11 ` Arseniy Krasnov
2023-12-13 17:56 ` Michael S. Tsirkin
2023-12-14 8:45 ` Stefano Garzarella
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=20231212105322-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=avkrasnov@salutedevices.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).