diff options
| author | David S. Miller <davem@davemloft.net> | 2017-01-26 04:47:31 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-01-26 04:47:31 +0100 |
| commit | 7480888f27e080ad5addb51456b2e03514721c3a (patch) | |
| tree | 79ca0e6d3f49de50e4f20e4724400dbd47df5ba4 /drivers/net/virtio_net.c | |
| parent | net: dsa: Bring back device detaching in dsa_slave_suspend() (diff) | |
| parent | r8152: check rx after napi is enabled (diff) | |
| download | linux-7480888f27e080ad5addb51456b2e03514721c3a.tar.xz linux-7480888f27e080ad5addb51456b2e03514721c3a.zip | |
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 '')
0 files changed, 0 insertions, 0 deletions