summaryrefslogtreecommitdiffstats
path: root/Documentation/lockup-watchdogs.txt
diff options
context:
space:
mode:
authorDavid Vrabel <david.vrabel@citrix.com>2014-12-18 12:13:06 +0100
committerDavid S. Miller <davem@davemloft.net>2014-12-18 18:49:49 +0100
commit26c0e102585d5a4d311f5d6eb7f524d288e7f6b7 (patch)
tree6ae75952d9356a1e82d175c67501506ad535cace /Documentation/lockup-watchdogs.txt
parentMAINTAINERS: changes for wireless (diff)
downloadlinux-26c0e102585d5a4d311f5d6eb7f524d288e7f6b7.tar.xz
linux-26c0e102585d5a4d311f5d6eb7f524d288e7f6b7.zip
xen-netback: support frontends without feature-rx-notify again
Commit bc96f648df1bbc2729abbb84513cf4f64273a1f1 (xen-netback: make feature-rx-notify mandatory) incorrectly assumed that there were no frontends in use that did not support this feature. But the frontend driver in MiniOS does not and since this is used by (qemu) stubdoms, these stopped working. Netback sort of works as-is in this mode except: - If there are no Rx requests and the internal Rx queue fills, only the drain timeout will wake the thread. The default drain timeout of 10 s would give unacceptable pauses. - If an Rx stall was detected and the internal Rx queue is drained, then the Rx thread would never wake. Handle these two cases (when feature-rx-notify is disabled) by: - Reducing the drain timeout to 30 ms. - Disabling Rx stall detection. Reported-by: John <jw@nuclearfallout.net> Tested-by: John <jw@nuclearfallout.net> Signed-off-by: David Vrabel <david.vrabel@citrix.com> Reviewed-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/lockup-watchdogs.txt')
0 files changed, 0 insertions, 0 deletions