From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, bjorn.andersson@linaro.org,
mka@chromium.org, evgreen@chromium.org, cpratapa@codeaurora.org,
avuyyuru@codeaurora.org, jponduru@codeaurora.org,
subashab@codeaurora.org, elder@kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] net: ipa: improve RX buffer replenishing
Date: Fri, 04 Feb 2022 10:40:12 +0000 [thread overview]
Message-ID: <164397121292.5815.16093042564142954985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220203170927.770572-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 3 Feb 2022 11:09:17 -0600 you wrote:
> This series revises the algorithm used for replenishing receive
> buffers on RX endpoints. Currently there are two atomic variables
> that track how many receive buffers can be sent to the hardware.
> The new algorithm obviates the need for those, by just assuming we
> always want to provide the hardware with buffers until it can hold
> no more.
>
> [...]
Here is the summary with links:
- [net-next,01/10] net: ipa: kill replenish_saved
https://git.kernel.org/netdev/net-next/c/a9bec7ae70c1
- [net-next,02/10] net: ipa: allocate transaction before pages when replenishing
https://git.kernel.org/netdev/net-next/c/b4061c136b56
- [net-next,03/10] net: ipa: increment backlog in replenish caller
https://git.kernel.org/netdev/net-next/c/4b22d8419549
- [net-next,04/10] net: ipa: decide on doorbell in replenish loop
https://git.kernel.org/netdev/net-next/c/b9dbabc5ca84
- [net-next,05/10] net: ipa: allocate transaction in replenish loop
(no matching commit)
- [net-next,06/10] net: ipa: don't use replenish_backlog
https://git.kernel.org/netdev/net-next/c/d0ac30e74ea0
- [net-next,07/10] net: ipa: introduce gsi_channel_trans_idle()
https://git.kernel.org/netdev/net-next/c/5fc7f9ba2e51
- [net-next,08/10] net: ipa: kill replenish_backlog
https://git.kernel.org/netdev/net-next/c/09b337dedaca
- [net-next,09/10] net: ipa: replenish after delivering payload
https://git.kernel.org/netdev/net-next/c/5d6ac24fb10f
- [net-next,10/10] net: ipa: determine replenish doorbell differently
https://git.kernel.org/netdev/net-next/c/9654d8c462ce
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-04 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 17:09 [PATCH net-next 00/10] net: ipa: improve RX buffer replenishing Alex Elder
2022-02-03 17:09 ` [PATCH net-next 01/10] net: ipa: kill replenish_saved Alex Elder
2022-02-03 17:09 ` [PATCH net-next 02/10] net: ipa: allocate transaction before pages when replenishing Alex Elder
2022-02-03 17:09 ` [PATCH net-next 03/10] net: ipa: increment backlog in replenish caller Alex Elder
2022-02-03 17:09 ` [PATCH net-next 04/10] net: ipa: decide on doorbell in replenish loop Alex Elder
2022-02-03 17:09 ` [PATCH net-next 05/10] net: ipa: allocate transaction " Alex Elder
2022-02-03 17:09 ` [PATCH net-next 06/10] net: ipa: don't use replenish_backlog Alex Elder
2022-02-03 17:09 ` [PATCH net-next 07/10] net: ipa: introduce gsi_channel_trans_idle() Alex Elder
2022-02-03 17:09 ` [PATCH net-next 08/10] net: ipa: kill replenish_backlog Alex Elder
2022-02-03 17:09 ` [PATCH net-next 09/10] net: ipa: replenish after delivering payload Alex Elder
2022-02-03 17:09 ` [PATCH net-next 10/10] net: ipa: determine replenish doorbell differently Alex Elder
2022-02-04 10:40 ` 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=164397121292.5815.16093042564142954985.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avuyyuru@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=jponduru@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox