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 v9 3/4] vsock: update SO_RCVLOWAT setting callback
Date: Thu, 14 Dec 2023 05:29:38 -0500 [thread overview]
Message-ID: <20231214052502-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231214091947.395892-4-avkrasnov@salutedevices.com>
On Thu, Dec 14, 2023 at 12:19:46PM +0300, Arseniy Krasnov wrote:
> Do not return if transport callback for SO_RCVLOWAT is set (only in
> error case). In this case we don't need to set 'sk_rcvlowat' field in
> each transport - only in 'vsock_set_rcvlowat()'. Also, if 'sk_rcvlowat'
> is now set only in af_vsock.c, change callback name from 'set_rcvlowat'
> to 'notify_set_rcvlowat'.
>
> Signed-off-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Maybe squash this with patch 2/4?
> ---
> Changelog:
> v3 -> v4:
> * Rename 'set_rcvlowat' to 'notify_set_rcvlowat'.
> * Commit message updated.
>
> include/net/af_vsock.h | 2 +-
> net/vmw_vsock/af_vsock.c | 9 +++++++--
> net/vmw_vsock/hyperv_transport.c | 4 ++--
> 3 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
> index e302c0e804d0..535701efc1e5 100644
> --- a/include/net/af_vsock.h
> +++ b/include/net/af_vsock.h
> @@ -137,7 +137,6 @@ struct vsock_transport {
> u64 (*stream_rcvhiwat)(struct vsock_sock *);
> bool (*stream_is_active)(struct vsock_sock *);
> bool (*stream_allow)(u32 cid, u32 port);
> - int (*set_rcvlowat)(struct vsock_sock *vsk, int val);
>
> /* SEQ_PACKET. */
> ssize_t (*seqpacket_dequeue)(struct vsock_sock *vsk, struct msghdr *msg,
> @@ -168,6 +167,7 @@ struct vsock_transport {
> struct vsock_transport_send_notify_data *);
> /* sk_lock held by the caller */
> void (*notify_buffer_size)(struct vsock_sock *, u64 *);
> + int (*notify_set_rcvlowat)(struct vsock_sock *vsk, int val);
>
> /* Shutdown. */
> int (*shutdown)(struct vsock_sock *, int);
> diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
> index 816725af281f..54ba7316f808 100644
> --- a/net/vmw_vsock/af_vsock.c
> +++ b/net/vmw_vsock/af_vsock.c
> @@ -2264,8 +2264,13 @@ static int vsock_set_rcvlowat(struct sock *sk, int val)
>
> transport = vsk->transport;
>
> - if (transport && transport->set_rcvlowat)
> - return transport->set_rcvlowat(vsk, val);
> + if (transport && transport->notify_set_rcvlowat) {
> + int err;
> +
> + err = transport->notify_set_rcvlowat(vsk, val);
> + if (err)
> + return err;
> + }
>
> WRITE_ONCE(sk->sk_rcvlowat, val ? : 1);
> return 0;
I would s
> diff --git a/net/vmw_vsock/hyperv_transport.c b/net/vmw_vsock/hyperv_transport.c
> index 7cb1a9d2cdb4..e2157e387217 100644
> --- a/net/vmw_vsock/hyperv_transport.c
> +++ b/net/vmw_vsock/hyperv_transport.c
> @@ -816,7 +816,7 @@ int hvs_notify_send_post_enqueue(struct vsock_sock *vsk, ssize_t written,
> }
>
> static
> -int hvs_set_rcvlowat(struct vsock_sock *vsk, int val)
> +int hvs_notify_set_rcvlowat(struct vsock_sock *vsk, int val)
> {
> return -EOPNOTSUPP;
> }
> @@ -856,7 +856,7 @@ static struct vsock_transport hvs_transport = {
> .notify_send_pre_enqueue = hvs_notify_send_pre_enqueue,
> .notify_send_post_enqueue = hvs_notify_send_post_enqueue,
>
> - .set_rcvlowat = hvs_set_rcvlowat
> + .notify_set_rcvlowat = hvs_notify_set_rcvlowat
> };
>
> static bool hvs_check_transport(struct vsock_sock *vsk)
> --
> 2.25.1
next prev parent reply other threads:[~2023-12-14 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 9:19 [PATCH net-next v9 0/4] send credit update during setting SO_RCVLOWAT Arseniy Krasnov
2023-12-14 9:19 ` [PATCH net-next v9 1/4] virtio/vsock: fix logic which reduces credit update messages Arseniy Krasnov
2023-12-14 9:19 ` [PATCH net-next v9 2/4] virtio/vsock: send credit update during setting SO_RCVLOWAT Arseniy Krasnov
2023-12-14 9:57 ` Stefano Garzarella
2023-12-14 10:24 ` Michael S. Tsirkin
2023-12-14 9:19 ` [PATCH net-next v9 3/4] vsock: update SO_RCVLOWAT setting callback Arseniy Krasnov
2023-12-14 10:29 ` Michael S. Tsirkin [this message]
2023-12-14 10:52 ` Arseniy Krasnov
2023-12-14 11:17 ` Michael S. Tsirkin
2023-12-14 12:52 ` Arseniy Krasnov
2023-12-14 9:19 ` [PATCH net-next v9 4/4] vsock/test: two tests to check credit update logic Arseniy Krasnov
2023-12-14 9:56 ` [PATCH net-next v9 0/4] send credit update during setting SO_RCVLOWAT 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=20231214052502-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).