diff options
author | David S. Miller <davem@davemloft.net> | 2017-01-25 22:47:31 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-01-25 22:47:31 -0500 |
commit | 7480888f27e080ad5addb51456b2e03514721c3a (patch) | |
tree | 79ca0e6d3f49de50e4f20e4724400dbd47df5ba4 /include/xen | |
parent | f154be241d22298d2b63c9b613f619fa1086ea75 (diff) | |
parent | 7489bdadb7d17d3c81e39b85688500f700beb790 (diff) |
Merge branch 'r8152-napi-fixes'
Hayes Wang says:
====================
r8152: fix scheduling napi
v3:
simply the argument for patch #3. Replace &tp->napi with napi.
v2:
Add smp_mb__after_atomic() for patch #1.
v1:
Scheduling the napi during the following periods would let it be ignored.
And the events wouldn't be handled until next napi_schedule() is called.
1. after napi_disable and before napi_enable().
2. after all actions of napi function is completed and before calling
napi_complete().
If no next napi_schedule() is called, tx or rx would stop working.
In order to avoid these situations, the followings solutions are applied.
1. prevent start_xmit() from calling napi_schedule() during runtime suspend
or after napi_disable().
2. re-schedule the napi for tx if it is necessary.
3. check if any rx is finished or not after napi_enable().
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/xen')
0 files changed, 0 insertions, 0 deletions