netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: jiangyiwen <jiangyiwen@huawei.com>,
	stefanha@redhat.com, stefanha@gmail.com, netdev@vger.kernel.org,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC] Discuss about an new idea "Vsock over Virtio-net"
Date: Fri, 30 Nov 2018 08:34:54 -0500	[thread overview]
Message-ID: <20181130083310-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <55352308-9ceb-413e-44f6-e3dfd8f642cc@redhat.com>

On Fri, Nov 30, 2018 at 08:55:17PM +0800, Jason Wang wrote:
> 
> On 2018/11/30 下午8:52, Michael S. Tsirkin wrote:
> > > >    If you want to compare it with
> > > > something that would be TCP or QUIC.  The fundamental difference between
> > > > virtio-vsock and e.g. TCP is that TCP operates in a packet loss environment.
> > > > So they are using timers for reliability, and receiver is always free to
> > > > discard any unacked data.
> > > Virtio-net knows nothing above L2, so they are totally transparent to device
> > > itself. I still don't get why not using virtio-net instead.
> > > 
> > > 
> > > Thanks
> > Is your question why is virtio-vsock used instead of TCP on top of IP
> > on top of virtio-net?
> > 
> > 
> 
> No, my question is why not do vsock through virtio-net.
> 
> Thanks

Because apps need reliability, multiplexing and flow control and
virtio-net does not provide it.

-- 
MST

  parent reply	other threads:[~2018-12-01  0:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  3:56 [RFC] Discuss about an new idea "Vsock over Virtio-net" jiangyiwen
2018-11-15  4:19 ` Jason Wang
2018-11-15  6:46   ` jiangyiwen
2018-11-15  6:49     ` jiangyiwen
2018-11-15  8:19     ` Jason Wang
2018-11-15  9:02       ` jiangyiwen
2018-11-15  9:21         ` Jason Wang
2018-11-16  2:32           ` jiangyiwen
2018-11-16  6:35             ` Jason Wang
2018-11-15  7:04 ` Michael S. Tsirkin
2018-11-15  7:38   ` jiangyiwen
2018-11-15  8:10     ` Michael S. Tsirkin
2018-11-15  8:27       ` Jason Wang
2018-11-15  8:38       ` jiangyiwen
2018-11-15  8:24   ` Jason Wang
2018-11-29 14:00     ` Michael S. Tsirkin
2018-11-30 12:45       ` Jason Wang
2018-11-30 12:52         ` Michael S. Tsirkin
2018-11-30 12:55           ` Jason Wang
2018-11-30 13:10             ` Jason Wang
2018-11-30 13:40               ` Michael S. Tsirkin
2018-12-03  3:10                 ` jiangyiwen
2018-12-04  1:31                   ` Michael S. Tsirkin
2018-12-04  2:21                     ` jiangyiwen
2018-12-04  4:08                       ` Michael S. Tsirkin
2018-12-04  6:01                         ` jiangyiwen
2018-11-30 13:34             ` Michael S. Tsirkin [this message]
2018-11-15  9:36 ` Yan Vugenfirer
2018-11-16  2:37   ` jiangyiwen

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=20181130083310-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jiangyiwen@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stefanha@gmail.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).