From: Arseny Krasnov <arseny.krasnov@kaspersky.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] vhost/vsock: support for SOCK_SEQPACKET socket.
Date: Sat, 2 Jan 2021 13:12:13 +0300 [thread overview]
Message-ID: <ff5993ea-7001-78fa-ec2f-dda1ae606b36@kaspersky.com> (raw)
In-Reply-To: <20201230155742-mutt-send-email-mst@kernel.org>
> oh this was not threaded correctly so I did not see rest of
> patches. ignore this pls will respond there.
Sorry, i'll resend whole patchset ASAP in one thread.
On 30.12.2020 23:58, Michael S. Tsirkin wrote:
> On Wed, Dec 30, 2020 at 03:56:03PM -0500, Michael S. Tsirkin wrote:
>> On Tue, Dec 29, 2020 at 02:06:33PM +0300, Arseny Krasnov wrote:
>>> This patch simply adds transport ops and removes
>>> ignore of non-stream type of packets.
>>>
>>> Signed-off-by: Arseny Krasnov <arseny.krasnov@kaspersky.com>
>> How is this supposed to work? virtio vsock at the moment
>> has byte level end to end credit accounting at the
>> protocol level. I suspect some protocol changes involving
>> more than this tweak would
>> be needed to properly support anything that isn't a stream.
>
> oh this was not threaded correctly so I did not see rest of
> patches. ignore this pls will respond there.
>
>>> ---
>>> drivers/vhost/vsock.c | 6 ++++--
>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c
>>> index a483cec31d5c..4a36ef1c52d0 100644
>>> --- a/drivers/vhost/vsock.c
>>> +++ b/drivers/vhost/vsock.c
>>> @@ -346,8 +346,7 @@ vhost_vsock_alloc_pkt(struct vhost_virtqueue *vq,
>>> return NULL;
>>> }
>>>
>>> - if (le16_to_cpu(pkt->hdr.type) == VIRTIO_VSOCK_TYPE_STREAM)
>>> - pkt->len = le32_to_cpu(pkt->hdr.len);
>>> + pkt->len = le32_to_cpu(pkt->hdr.len);
>>>
>>> /* No payload */
>>> if (!pkt->len)
>>> @@ -416,6 +415,9 @@ static struct virtio_transport vhost_transport = {
>>> .stream_is_active = virtio_transport_stream_is_active,
>>> .stream_allow = virtio_transport_stream_allow,
>>>
>>> + .seqpacket_seq_send_len = virtio_transport_seqpacket_seq_send_len,
>>> + .seqpacket_seq_get_len = virtio_transport_seqpacket_seq_get_len,
>>> +
>>> .notify_poll_in = virtio_transport_notify_poll_in,
>>> .notify_poll_out = virtio_transport_notify_poll_out,
>>> .notify_recv_init = virtio_transport_notify_recv_init,
>>> --
>>> 2.25.1
>
prev parent reply other threads:[~2021-01-02 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 11:06 Arseny Krasnov
2020-12-30 20:55 ` Michael S. Tsirkin
2020-12-30 20:58 ` Michael S. Tsirkin
2021-01-02 10:12 ` Arseny Krasnov [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=ff5993ea-7001-78fa-ec2f-dda1ae606b36@kaspersky.com \
--to=arseny.krasnov@kaspersky.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®