From: Grygorii Strashko <grygorii.strashko@ti.com>
To: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Eric Dumazet <edumazet@google.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH net-next 0/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion
Date: Fri, 6 Aug 2021 01:55:30 +0300 [thread overview]
Message-ID: <20210805225532.2667-1-grygorii.strashko@ti.com> (raw)
hi
The intention of this series is to fully enable hard irqs deferral feature
(hrtimers based HW IRQ coalescing) from Eric Dumazet [1] for TI K3 CPSW driver
by using napi_complete_done() in TX completion path, so the combination of
parameters (/sys/class/net/ethX/):
napi_defer_hard_irqs
gro_flush_timeout
can be used for hard irqs deferral.
The Patch 1 is required before enabling hard irqs deferral feature to avoid
"Unbalanced enable" issue if gro_flush_timeout is configured while
(napi_defer_hard_irqs == 0).
It's a bit sad that it can not be configured per RX/TX separately.
[1] https://lore.kernel.org/netdev/20200422161329.56026-1-edumazet@google.com/
Grygorii Strashko (1):
net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX
completion
Vignesh Raghavendra (1):
net: ti: am65-cpsw-nuss: fix RX IRQ state after .ndo_stop()
drivers/net/ethernet/ti/am65-cpsw-nuss.c | 23 ++++++++++++++++-------
drivers/net/ethernet/ti/am65-cpsw-nuss.h | 2 ++
2 files changed, 18 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-05 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 22:55 Grygorii Strashko [this message]
2021-08-05 22:55 ` [PATCH net-next 1/2] net: ti: am65-cpsw-nuss: fix RX IRQ state after .ndo_stop() Grygorii Strashko
2021-08-05 22:55 ` [PATCH net-next 2/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion Grygorii Strashko
2021-08-06 10:10 ` [PATCH net-next 0/2] " patchwork-bot+netdevbpf
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=20210805225532.2667-1-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=netdev@vger.kernel.org \
--cc=vigneshr@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox