diff options
| author | Alex Elder <[email protected]> | 2021-02-01 11:28:49 -0600 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2021-02-02 17:42:36 -0800 |
| commit | a65c0288b355a8bb71f43cf9b4c33ada51e0ec26 (patch) | |
| tree | e14301c2236225df86c285de2fcfa0973d3e3e6e /tools/perf/scripts/python | |
| parent | 4fef691c9b6ab5ed92b874bc6ddfb14a34c650ab (diff) | |
net: ipa: don't disable interrupt on suspend
No completion interrupts will occur while an endpoint is suspended,
nor when a channel has been stopped for suspend. So there's no need
to disable the interrupt during suspend and re-enable it when
resuming. Without any interrupts occurring, there is no need to
disable/re-enable NAPI for channel suspend/resume either.
We'll only enable NAPI and the interrupt when we first start the
channel, and disable it again only when it's "really" stopped.
To accomplish this, move the enable/disable calls out of
__gsi_channel_start() and __gsi_channel_stop(), and into
gsi_channel_start() and gsi_channel_stop() instead.
Add a call to napi_synchronize() to gsi_channel_suspend(), to ensure
NAPI polling is done before moving on.
Signed-off-by: Alex Elder <[email protected]>
Acked-by: Willem de Bruijn <[email protected]>
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions