From: patchwork-bot+netdevbpf@kernel.org
To: Voon Weifeng <weifeng.voon@intel.com>
Cc: davem@davemloft.net, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
joabreu@synopsys.com, kuba@kernel.org, peppe.cavallaro@st.com,
andrew@lunn.ch, alexandre.torgue@st.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, boon.leong.ong@intel.com,
vee.khee.wong@intel.com
Subject: Re: [PATCH v2 net-next 0/5] net: stmmac: enable multi-vector MSI
Date: Fri, 26 Mar 2021 21:50:10 +0000 [thread overview]
Message-ID: <161679541097.17455.17342387440492933878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210325173916.13203-1-weifeng.voon@intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 26 Mar 2021 01:39:11 +0800 you wrote:
> This patchset adds support for multi MSI interrupts in addition to
> current single common interrupt implementation. Each MSI interrupt is tied
> to a newly introduce interrupt service routine(ISR). Hence, each interrupt
> will only go through the corresponding ISR.
>
> In order to increase the efficiency, enabling multi MSI interrupt will
> automatically select the interrupt mode configuration INTM=1. When INTM=1,
> the TX/RX transfer complete signal will only asserted on corresponding
> sbd_perch_tx_intr_o[] or sbd_perch_rx_intr_o[] without asserting signal
> on the common sbd_intr_o. Hence, for each TX/RX interrupts, only the
> corresponding ISR will be triggered.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/5] net: stmmac: introduce DMA interrupt status masking per traffic direction
https://git.kernel.org/netdev/net-next/c/7e1c520c0d20
- [v2,net-next,2/5] net: stmmac: make stmmac_interrupt() function more friendly to MSI
https://git.kernel.org/netdev/net-next/c/29e6573c61aa
- [v2,net-next,3/5] net: stmmac: introduce MSI Interrupt routines for mac, safety, RX & TX
https://git.kernel.org/netdev/net-next/c/8532f613bc78
- [v2,net-next,4/5] stmmac: intel: add support for multi-vector msi and msi-x
https://git.kernel.org/netdev/net-next/c/b42446b9b37b
- [v2,net-next,5/5] net: stmmac: use interrupt mode INTM=1 for multi-MSI
https://git.kernel.org/netdev/net-next/c/6ccf12ae111e
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:[~2021-03-26 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 17:39 [PATCH v2 net-next 0/5] net: stmmac: enable multi-vector MSI Voon Weifeng
2021-03-25 17:39 ` [PATCH v2 net-next 1/5] net: stmmac: introduce DMA interrupt status masking per traffic direction Voon Weifeng
2021-03-25 17:39 ` [PATCH v2 net-next 2/5] net: stmmac: make stmmac_interrupt() function more friendly to MSI Voon Weifeng
2021-03-25 17:39 ` [PATCH v2 net-next 3/5] net: stmmac: introduce MSI Interrupt routines for mac, safety, RX & TX Voon Weifeng
2021-03-25 17:39 ` [PATCH v2 net-next 4/5] stmmac: intel: add support for multi-vector msi and msi-x Voon Weifeng
2021-03-26 9:07 ` Ong, Boon Leong
2021-03-25 17:39 ` [PATCH v2 net-next 5/5] net: stmmac: use interrupt mode INTM=1 for multi-MSI Voon Weifeng
2021-03-26 21: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=161679541097.17455.17342387440492933878.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--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=vee.khee.wong@intel.com \
--cc=weifeng.voon@intel.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