From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, kernel@axis.com, larper@axis.com,
srinivas.kandagatla@st.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: stmmac: only enable DMA interrupts when ready
Date: Fri, 25 Feb 2022 10:50:11 +0000 [thread overview]
Message-ID: <164578621107.20500.7059281134747424686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220224113829.1092859-1-vincent.whitchurch@axis.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 24 Feb 2022 12:38:29 +0100 you wrote:
> In this driver's ->ndo_open() callback, it enables DMA interrupts,
> starts the DMA channels, then requests interrupts with request_irq(),
> and then finally enables napi.
>
> If RX DMA interrupts are received before napi is enabled, no processing
> is done because napi_schedule_prep() will return false. If the network
> has a lot of broadcast/multicast traffic, then the RX ring could fill up
> completely before napi is enabled. When this happens, no further RX
> interrupts will be delivered, and the driver will fail to receive any
> packets.
>
> [...]
Here is the summary with links:
- [v2] net: stmmac: only enable DMA interrupts when ready
https://git.kernel.org/netdev/net/c/087a7b944c5d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-25 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 11:38 [PATCH v2] net: stmmac: only enable DMA interrupts when ready Vincent Whitchurch
2022-02-24 12:53 ` Denis Kirjanov
2022-02-24 13:40 ` Vincent Whitchurch
2022-02-25 10:50 ` patchwork-bot+netdevbpf [this message]
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=164578621107.20500.7059281134747424686.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kernel@axis.com \
--cc=kuba@kernel.org \
--cc=larper@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=srinivas.kandagatla@st.com \
--cc=vincent.whitchurch@axis.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;
as well as URLs for NNTP newsgroup(s).