From: Hauke Mehrtens <hauke@hauke-m.de>
To: davem@davemloft.net
Cc: kuba@kernel.org, netdev@vger.kernel.org,
martin.blumenstingl@googlemail.com, eric.dumazet@gmail.com,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH v2 0/4] net: lantiq: Fix bugs in NAPI handling
Date: Sat, 12 Sep 2020 21:36:25 +0200 [thread overview]
Message-ID: <20200912193629.1586-1-hauke@hauke-m.de> (raw)
This fixes multiple bugs in the NAPI handling.
Changes since:
v1:
- removed stable tag from "net: lantiq: use netif_tx_napi_add() for TX NAPI"
- Check the NAPI budged in "net: lantiq: Use napi_complete_done()"
- Add extra fix "net: lantiq: Disable IRQs only if NAPI gets scheduled"
Hauke Mehrtens (4):
net: lantiq: Wake TX queue again
net: lantiq: use netif_tx_napi_add() for TX NAPI
net: lantiq: Use napi_complete_done()
net: lantiq: Disable IRQs only if NAPI gets scheduled
drivers/net/ethernet/lantiq_xrx200.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
--
2.20.1
next reply other threads:[~2020-09-12 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 19:36 Hauke Mehrtens [this message]
2020-09-12 19:36 ` [PATCH v2 1/4] net: lantiq: Wake TX queue again Hauke Mehrtens
2020-09-12 19:36 ` [PATCH v2 2/4] net: lantiq: use netif_tx_napi_add() for TX NAPI Hauke Mehrtens
2020-09-12 19:36 ` [PATCH v2 3/4] net: lantiq: Use napi_complete_done() Hauke Mehrtens
2020-09-12 19:36 ` [PATCH v2 4/4] net: lantiq: Disable IRQs only if NAPI gets scheduled Hauke Mehrtens
2020-09-14 20:54 ` Jakub Kicinski
2020-09-14 23:06 ` Hauke Mehrtens
2020-09-12 20:22 ` [PATCH v2 0/4] net: lantiq: Fix bugs in NAPI handling Martin Blumenstingl
2020-09-14 21:54 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200912193629.1586-1-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.