From: Arseniy Krasnov <avkrasnov@salutedevices.com>
To: Amery Hung <ameryhung@gmail.com>
Cc: <stefanha@redhat.com>, <sgarzare@redhat.com>, <mst@redhat.com>,
<jasowang@redhat.com>, <xuanzhuo@linux.alibaba.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <kys@microsoft.com>,
<haiyangz@microsoft.com>, <wei.liu@kernel.org>,
<decui@microsoft.com>, <bryantan@vmware.com>, <vdasa@vmware.com>,
<pv-drivers@vmware.com>, <dan.carpenter@linaro.org>,
<simon.horman@corigine.com>, <oxffffaa@gmail.com>,
<kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-hyperv@vger.kernel.org>, <bpf@vger.kernel.org>,
<bobby.eshleman@bytedance.com>, <jiang.wang@bytedance.com>,
<amery.hung@bytedance.com>, <xiyou.wangcong@gmail.com>,
<kernel@sberdevices.ru>
Subject: Re: [RFC PATCH net-next v6 03/14] af_vsock: support multi-transport datagrams
Date: Mon, 29 Jul 2024 08:12:07 +0300 [thread overview]
Message-ID: <7416dd44-4f89-bd97-4925-1aa5a2588e76@salutedevices.com> (raw)
In-Reply-To: <CAMB2axNUbWD9=Xg8TkB8XBmjuNw9f==Njzvh4-OP8kNw40O0Lw@mail.gmail.com>
On 29.07.2024 00:53, Amery Hung wrote:
> On Sun, Jul 28, 2024 at 1:40 PM Arseniy Krasnov
> <avkrasnov@salutedevices.com> wrote:
>>
>> Hi Amery
>>
>>> /* Transport features flags */
>>> /* Transport provides host->guest communication */
>>> -#define VSOCK_TRANSPORT_F_H2G 0x00000001
>>> +#define VSOCK_TRANSPORT_F_H2G 0x00000001
>>> /* Transport provides guest->host communication */
>>> -#define VSOCK_TRANSPORT_F_G2H 0x00000002
>>> -/* Transport provides DGRAM communication */
>>> -#define VSOCK_TRANSPORT_F_DGRAM 0x00000004
>>> +#define VSOCK_TRANSPORT_F_G2H 0x00000002
>>> +/* Transport provides fallback for DGRAM communication */
>>> +#define VSOCK_TRANSPORT_F_DGRAM_FALLBACK 0x00000004
>>> /* Transport provides local (loopback) communication */
>>> -#define VSOCK_TRANSPORT_F_LOCAL 0x00000008
>>> +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008
>>
>> ^^^ This is refactoring ?
>>
>
> This part contains no functional change.
Ah I see, sorry )
Thanks, Arseniy
>
> Since virtio dgram uses transport_h2g/g2h instead of transport_dgram
> (renamed totransport_dgam_fallback to in this patch) of VMCI, we
> rename the flags here to describe the transport in a more accurate
> way.
>
> For a datagram vsock, during socket creation, if VMCI is present,
> transport_dgram will be registered as a fallback.
>
> During vsock_dgram_sendmsg(), we will always try to resolve the
> transport to transport_h2g/g2h/local first and then fallback on
> transport_dgram.
>
> Let me know if there is anything that is confusing here.
>
>>
>>> + /* During vsock_create(), the transport cannot be decided yet if
>>> + * using virtio. While for VMCI, it is transport_dgram_fallback.
>>
>>
>> I'm not English speaker, but 'decided' -> 'detected'/'resolved' ?
>>
>
> Not a native English speaker either, but I think resolve is also
> pretty accurate.
>
> Thanks,
> Amery
>
>>
>>
>> Thanks, Arseniy
next prev parent reply other threads:[~2024-07-29 5:24 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 21:25 [RFC PATCH net-next v6 00/14] virtio/vsock: support datagrams Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 01/14] af_vsock: generalize vsock_dgram_recvmsg() to all transports Amery Hung
2024-07-15 8:02 ` Luigi Leonardi
2024-07-15 23:39 ` Amery Hung
2024-07-29 19:25 ` Arseniy Krasnov
2024-07-10 21:25 ` [RFC PATCH net-next v6 02/14] af_vsock: refactor transport lookup code Amery Hung
2024-07-25 6:29 ` Arseniy Krasnov
2024-07-28 22:10 ` Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 03/14] af_vsock: support multi-transport datagrams Amery Hung
2024-07-15 8:13 ` Arseniy Krasnov
2024-07-15 17:41 ` Amery Hung
2024-07-28 20:28 ` Arseniy Krasnov
2024-07-28 21:53 ` Amery Hung
2024-07-29 5:12 ` Arseniy Krasnov [this message]
2024-07-10 21:25 ` [RFC PATCH net-next v6 04/14] af_vsock: generalize bind table functions Amery Hung
2024-07-23 14:39 ` Stefano Garzarella
2024-07-28 18:52 ` Amery Hung
2024-07-30 8:00 ` Stefano Garzarella
2024-07-30 17:56 ` Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 05/14] af_vsock: use a separate dgram bind table Amery Hung
2024-07-23 14:41 ` Stefano Garzarella
2024-07-28 21:37 ` Amery Hung
2024-07-30 8:05 ` Stefano Garzarella
2024-07-10 21:25 ` [RFC PATCH net-next v6 06/14] virtio/vsock: add VIRTIO_VSOCK_TYPE_DGRAM Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 07/14] virtio/vsock: add common datagram send path Amery Hung
2024-07-23 14:42 ` Stefano Garzarella
2024-07-26 23:22 ` Amery Hung
2024-07-30 8:22 ` Stefano Garzarella
2024-07-29 20:00 ` Arseniy Krasnov
2024-07-29 22:51 ` Amery Hung
2024-07-30 5:09 ` Arseniy Krasnov
2024-07-10 21:25 ` [RFC PATCH net-next v6 08/14] af_vsock: add vsock_find_bound_dgram_socket() Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 09/14] virtio/vsock: add common datagram recv path Amery Hung
2024-07-23 14:42 ` Stefano Garzarella
2024-07-30 0:35 ` Amery Hung
2024-07-30 8:32 ` Stefano Garzarella
2024-07-10 21:25 ` [RFC PATCH net-next v6 10/14] virtio/vsock: add VIRTIO_VSOCK_F_DGRAM feature bit Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 11/14] vhost/vsock: implement datagram support Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 12/14] vsock/loopback: " Amery Hung
2024-08-01 12:18 ` Luigi Leonardi
2024-07-10 21:25 ` [RFC PATCH net-next v6 13/14] virtio/vsock: " Amery Hung
2024-07-11 23:02 ` Luigi Leonardi
2024-07-11 23:07 ` Amery Hung
2024-07-10 21:25 ` [RFC PATCH net-next v6 14/14] test/vsock: add vsock dgram tests Amery Hung
2024-07-20 19:58 ` Arseniy Krasnov
2024-07-23 14:43 ` Stefano Garzarella
2024-07-28 22:06 ` Amery Hung
2024-07-23 14:38 ` [RFC PATCH net-next v6 00/14] virtio/vsock: support datagrams Stefano Garzarella
2025-07-22 14:35 ` Stefano Garzarella
2025-07-26 5:53 ` Amery Hung
2025-07-29 12:40 ` 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=7416dd44-4f89-bd97-4925-1aa5a2588e76@salutedevices.com \
--to=avkrasnov@salutedevices.com \
--cc=amery.hung@bytedance.com \
--cc=ameryhung@gmail.com \
--cc=bobby.eshleman@bytedance.com \
--cc=bpf@vger.kernel.org \
--cc=bryantan@vmware.com \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=pv-drivers@vmware.com \
--cc=sgarzare@redhat.com \
--cc=simon.horman@corigine.com \
--cc=stefanha@redhat.com \
--cc=vdasa@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.liu@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--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®