> -Original Message-
> From: Stefan Puiu [mailto:stefan.p...@gmail.com]
> Sent: Monday, December 12, 2016 12:27 AM
> To: Yong Wang
> Cc: dev@dpdk.org; mac_le...@yahoo.com.hk
> Subject: Re: [PATCH] vmxnet3: fix Rx deadlock
>
> Hello and thanks for reviewing the patch.
>
> On Wed, Nov 30,
Hello and thanks for reviewing the patch.
On Wed, Nov 30, 2016 at 6:59 AM, Yong Wang wrote:
[...]
> I think a more accurate description is that the particular descriptor's
> generation bit never got flipped properly when an mbuf failed to be refilled
> which caused the rx stuck, rather than vmx
> -Original Message-
> From: Stefan Puiu [mailto:stefan.puiu at gmail.com]
> Sent: Monday, November 14, 2016 2:46 AM
> To: dev at dpdk.org
> Cc: mac_leehk at yahoo.com.hk; Yong Wang ;
> Stefan Puiu
> Subject: [PATCH] vmxnet3: fix Rx deadlock
>
> Our use case is that we have an app that ne
Our use case is that we have an app that needs to keep mbufs around
for a while. We've seen cases when calling vmxnet3_post_rx_bufs() from
vmxet3_recv_pkts(), it might not succeed to add any mbufs to any RX
descriptors (where it returns -err). Since there are no mbufs that the
virtual hardware can
Our use case is that we have an app that needs to keep mbufs around
for a while. We've seen cases when calling vmxnet3_post_rx_bufs() from
vmxet3_recv_pkts(), it might not succeed to add any mbufs to any RX
descriptors (where it returns -err). Since there are no mbufs that the
virtual hardware can
5 matches
Mail list logo
