Revision 42b5212fee4f57907e9415b18fe19c13e65574bc authored by David Vrabel on 02 February 2015, 16:57:51 UTC, committed by David S. Miller on 03 February 2015, 03:39:04 UTC
After commit e9d8b2c2968499c1f96563e6522c56958d5a1d0d (xen-netback: disable rogue vif in kthread context), a fatal (protocol) error would leave the guest Rx thread spinning, wasting CPU time. Commit ecf08d2dbb96d5a4b4bcc53a39e8d29cc8fef02e (xen-netback: reintroduce guest Rx stall detection) made this even worse by removing a cond_resched() from this path. Since a fatal error is non-recoverable, just allow the guest Rx thread to exit. This requires taking additional refs to the task so the thread exiting early is handled safely. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Reported-by: Julien Grall <julien.grall@linaro.org> Tested-by: Julien Grall <julien.grall@linaro.org> Acked-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent 5a2e87b
| File | Mode | Size |
|---|---|---|
| 00-INDEX | -rw-r--r-- | 918 bytes |
| blkio-controller.txt | -rw-r--r-- | 16.0 KB |
| cgroups.txt | -rw-r--r-- | 26.4 KB |
| cpuacct.txt | -rw-r--r-- | 1.9 KB |
| cpusets.txt | -rw-r--r-- | 36.0 KB |
| devices.txt | -rw-r--r-- | 4.3 KB |
| freezer-subsystem.txt | -rw-r--r-- | 4.8 KB |
| hugetlb.txt | -rw-r--r-- | 1.7 KB |
| memcg_test.txt | -rw-r--r-- | 8.3 KB |
| memory.txt | -rw-r--r-- | 36.0 KB |
| net_cls.txt | -rw-r--r-- | 1.2 KB |
| net_prio.txt | -rw-r--r-- | 2.5 KB |
| unified-hierarchy.txt | -rw-r--r-- | 15.9 KB |
Computing file changes ...
