search for: virtio_trasnport_send_pkt_info

...w 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_worker -> vhost_transport_send_pkt_work -> get pkt from send_pkt_list -> get vq input desc and then fill data to desc addr -> update used ring and then signal guest In the whole process, host don...

...w 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_worker -> vhost_transport_send_pkt_work -> get pkt from send_pkt_list -> get vq input desc and then fill data to desc addr -> update used ring and then signal guest In the whole process, host don...

...o 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_worker >> -> vhost_transport_send_pkt_work >> -> get pkt from send_pkt_list >> -> get vq input desc and then fill data to desc addr >> -> upd...

...o 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_worker >> -> vhost_transport_send_pkt_work >> -> get pkt from send_pkt_list >> -> get vq input desc and then fill data to desc addr >> -> upd...

...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_worker > -> vhost_transport_send_pkt_work > -> get pkt from send_pkt_list > -> get vq input desc and then fill data to desc addr > -> update used ring and then signa...

...) 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_worker >>> -> vhost_transport_send_pkt_work >>> -> get pkt from send_pkt_list >>> -> get vq input desc and then fill data to desc...

...o 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_worker >>>> -> vhost_transport_send_pkt_work >>>> -> get pkt from send_pkt_list >>>> -> get vq input desc and...

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