search for: recvmg

...it is different with socket. To vsock, I think host will >> not call ->recvmsg when it need to send message to guest. To net, >> vhost-net only as forwarding layer. > > Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? For vsock, Host->Guest, it's code flow as follows: Server call send() -> sendmsg(); (vsock_stream_sendmsg) -> virtio_trasnport_send_pkt_info -> alloc pkt, add pkt to send_pkt_list, wake up vhost_worker Vhost_work...

...it is different with socket. To vsock, I think host will >> not call ->recvmsg when it need to send message to guest. To net, >> vhost-net only as forwarding layer. > > Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? For vsock, Host->Guest, it's code flow as follows: Server call send() -> sendmsg(); (vsock_stream_sendmsg) -> virtio_trasnport_send_pkt_info -> alloc pkt, add pkt to send_pkt_list, wake up vhost_worker Vhost_work...

...th socket. To vsock, I think host will >>>> not call ->recvmsg when it need to send message to guest. To net, >>>> vhost-net only as forwarding layer. >>> Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? >> For vsock, Host->Guest, it's code flow as follows: >> Server call send() >> -> sendmsg(); (vsock_stream_sendmsg) >> -> virtio_trasnport_send_pkt_info >> -> alloc pkt, add pkt to...

...th socket. To vsock, I think host will >>>> not call ->recvmsg when it need to send message to guest. To net, >>>> vhost-net only as forwarding layer. >>> Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? >> For vsock, Host->Guest, it's code flow as follows: >> Server call send() >> -> sendmsg(); (vsock_stream_sendmsg) >> -> virtio_trasnport_send_pkt_info >> -> alloc pkt, add pkt to...

...o > get data, it is different with socket. To vsock, I think host will > not call ->recvmsg when it need to send message to guest. To net, > vhost-net only as forwarding layer. Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? If this doesn't work, we can have vsock specific receiving routine in vhost_net if VIRTIO_NET_F_VOSCK is negotiated. Generally, I think we should try out best to keep the exist sendmsg()/recvmsg() interfaces and only consider the alt...

...different with socket. To vsock, I think host will >>> not call ->recvmsg when it need to send message to guest. To net, >>> vhost-net only as forwarding layer. >> Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? > For vsock, Host->Guest, it's code flow as follows: > Server call send() > -> sendmsg(); (vsock_stream_sendmsg) > -> virtio_trasnport_send_pkt_info > -> alloc pkt, add pkt to send_pkt_list, wake...

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

...o vsock, I think host will >>>>> not call ->recvmsg when it need to send message to guest. To net, >>>>> vhost-net only as forwarding layer. >>>> Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? >>> For vsock, Host->Guest, it's code flow as follows: >>> Server call send() >>> -> sendmsg(); (vsock_stream_sendmsg) >>> -> virtio_trasnport_send_pkt_info >>> ->...

...hink host will >>>>>> not call ->recvmsg when it need to send message to guest. To net, >>>>>> vhost-net only as forwarding layer. >>>>> Know not much here, but is it possible to have a vsock(tap) to be passed to vhost_net and let vhost call its recvmgs()? Bascially it was a socket on host as well I believe? >>>> For vsock, Host->Guest, it's code flow as follows: >>>> Server call send() >>>> -> sendmsg(); (vsock_stream_sendmsg) >>>> -> virtio_trasnport_send_pkt_info >>&g...