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 _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
