Paul Durrant 11b57f9025 xen-netback: stop vif thread spinning if frontend is unresponsive ... The recent patch to improve guest receive side flow control (ca2f09f2) had a slight flaw in the wait condition for the vif thread in that any remaining skbs in the guest receive side netback internal queue would prevent the thread from sleeping. An unresponsive frontend can lead to a permanently non-empty internal queue and thus the thread will spin. In this case the thread should really sleep until the frontend becomes responsive again. This patch adds an extra flag to the vif which is set if the shared ring is full and cleared when skbs are drained into the shared ring. Thus, if the thread runs, finds the shared ring full and can make no progress the flag remains set. If the flag remains set then the thread will sleep, regardless of a non-empty queue, until the next event from the frontend. Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: David Vrabel <david.vrabel@citrix.com> Acked-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2014-01-09 23:05:46 -05:00
..
common.h	xen-netback: stop vif thread spinning if frontend is unresponsive	2014-01-09 23:05:46 -05:00
interface.c	Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/davem/net	2014-01-06 17:37:45 -05:00
Makefile
netback.c	xen-netback: stop vif thread spinning if frontend is unresponsive	2014-01-09 23:05:46 -05:00
xenbus.c	drivers/net/*: Fix FSF address in file headers	2013-12-06 12:37:55 -05:00