search for: virtio_net_f_vosck

...ferences, vhost-net use ->sendmsg to | >> | * forward information, however vsock only need to notify server | >> | * that data ready. */ | >> +------------------------------------------------------------------+ > > > When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. > > >> | >> | >> +------------------------------------------------------------------+ >> |VSOCK Core Mo...

...ferences, vhost-net use ->sendmsg to | >> | * forward information, however vsock only need to notify server | >> | * that data ready. */ | >> +------------------------------------------------------------------+ > > > When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. > > >> | >> | >> +------------------------------------------------------------------+ >> |VSOCK Core Mo...

...msg to | >>>> | * forward information, however vsock only need to notify server | >>>> | * that data ready. */ | >>>> +------------------------------------------------------------------+ >>> >>> When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. >>> >>> >>>> | >>>> | >>>> +---------------------------------------------------...

...msg to | >>>> | * forward information, however vsock only need to notify server | >>>> | * that data ready. */ | >>>> +------------------------------------------------------------------+ >>> >>> When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. >>> >>> >>>> | >>>> | >>>> +---------------------------------------------------...

.../* This point has some differences, vhost-net use ->sendmsg to | > | * forward information, however vsock only need to notify server | > | * that data ready. */ | > +------------------------------------------------------------------+ When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. > | > | > +------------------------------------------------------------------+ > |VSOCK Core Module...

...st-net use ->sendmsg to | >>> | * forward information, however vsock only need to notify server | >>> | * that data ready. */ | >>> +------------------------------------------------------------------+ >> >> When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. >> >> >>> | >>> | >>> +------------------------------------------------------------------+ &gt...

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

...to | >>>>> | * forward information, however vsock only need to notify server | >>>>> | * that data ready. */ | >>>>> +------------------------------------------------------------------+ >>>> When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. >>>> >>>> >>>>> | >>>>> | >>>>> +-----------------------------...

...>>>> | * forward information, however vsock only need to notify server | >>>>>> | * that data ready. */ | >>>>>> +------------------------------------------------------------------+ >>>>> When VIRTIO_NET_F_VOSCK is negotiated, we know that it's a vsock transport, we can then forward it to vsock core. >>>>> >>>>> >>>>>> | >>>>>> | >>>>>> +---------...