On 2018年03月16日 17:58, Greg Kurz wrote:
On Fri, 16 Mar 2018 16:05:17 +0800
Jason Wang wrote:
On 2018年03月08日 02:57, Greg Kurz wrote:
If the backend could not transmit a packet right away for some reason,
the packet is queued for asynchronous sending. The corresponding vq
On Fri, 16 Mar 2018 16:05:17 +0800
Jason Wang wrote:
> On 2018年03月08日 02:57, Greg Kurz wrote:
> > If the backend could not transmit a packet right away for some reason,
> > the packet is queued for asynchronous sending. The corresponding vq
> > element is tracked in the
On 2018年03月08日 02:57, Greg Kurz wrote:
If the backend could not transmit a packet right away for some reason,
the packet is queued for asynchronous sending. The corresponding vq
element is tracked in the async_tx.elem field of the VirtIONetQueue,
for later freeing when the transmission is
Ping ?
On Thu, 8 Mar 2018 10:38:56 +0530
"Nageswara R Sastry" wrote:
> Greg Kurz wrote on 08/03/2018 12:27:37 AM:
>
> > From: Greg Kurz
> > To: qemu-devel@nongnu.org
> > Cc: "Michael S. Tsirkin" , Jason Wang
> >
Greg Kurz wrote on 08/03/2018 12:27:37 AM:
> From: Greg Kurz
> To: qemu-devel@nongnu.org
> Cc: "Michael S. Tsirkin" , Jason Wang
> , R Nageswara Sastry
> Date: 08/03/2018 12:27 AM
> Subject: [PATCH]
If the backend could not transmit a packet right away for some reason,
the packet is queued for asynchronous sending. The corresponding vq
element is tracked in the async_tx.elem field of the VirtIONetQueue,
for later freeing when the transmission is complete.
If a reset happens before