On Tue, Jul 14, 2015 at 04:34:19PM +0800, Wen Congyang wrote:
> On 07/14/2015 03:53 PM, Fam Zheng wrote:
> > Since a90a742 "tap: Drop tap_can_send", all nics that returns false from
> > .can_receive() are required to explicitly flush the incoming queue when the
> > status of it is changing back to
On Tue, Jul 14, 2015 at 03:53:29PM +0800, Fam Zheng wrote:
> Since a90a742 "tap: Drop tap_can_send", all nics that returns false from
> .can_receive() are required to explicitly flush the incoming queue when the
> status of it is changing back to true, otherwise the backend will sop
> processing mo
On 07/14/2015 03:53 PM, Fam Zheng wrote:
> Since a90a742 "tap: Drop tap_can_send", all nics that returns false from
> .can_receive() are required to explicitly flush the incoming queue when the
> status of it is changing back to true, otherwise the backend will sop
> processing more rx packets.
>
Since a90a742 "tap: Drop tap_can_send", all nics that returns false from
.can_receive() are required to explicitly flush the incoming queue when the
status of it is changing back to true, otherwise the backend will sop
processing more rx packets.
The purpose of this callback is to tell the peer ba
