diff options
| author | David Vrabel <david.vrabel@citrix.com> | 2014-12-18 11:13:06 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-12-18 12:49:49 -0500 |
| commit | 26c0e102585d5a4d311f5d6eb7f524d288e7f6b7 (patch) | |
| tree | 6ae75952d9356a1e82d175c67501506ad535cace /drivers/leds | |
| parent | 0e324cf640fbd517615071c336fd4148fb5ce578 (diff) | |
| download | linux-26c0e102585d5a4d311f5d6eb7f524d288e7f6b7.tar.bz2 | |
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 'drivers/leds')
0 files changed, 0 insertions, 0 deletions