From: patchwork-bot+netdevbpf@kernel.org
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, maciej.fijalkowski@intel.com,
simon.horman@corigine.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] net: renesas: rswitch: Improve perfromance of TX/RX
Date: Sat, 10 Jun 2023 18:53:46 +0000 [thread overview]
Message-ID: <168642322622.21298.7526575301146103242.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230608022007.1866372-1-yoshihiro.shimoda.uh@renesas.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 8 Jun 2023 11:20:05 +0900 you wrote:
> This patch series is based on net-next.git / main branch [1]. This patch
> series can improve perfromance of TX in a specific condition. The previous code
> used "global rate limiter" feature so that this is possible to cause
> performance down if we use multiple ports at the same time. To resolve this
> issue, use "hardware pause" features of GWCA and COMA. Note that this is not
> related to the ethernet PAUSE frames.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] net: renesas: rswitch: Use napi_gro_receive() in RX
https://git.kernel.org/netdev/net-next/c/dc510c6d2ecf
- [net-next,v4,2/2] net: renesas: rswitch: Use hardware pause features
https://git.kernel.org/netdev/net-next/c/c87bd91e34e1
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:[~2023-06-10 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 2:20 [PATCH net-next v4 0/2] net: renesas: rswitch: Improve perfromance of TX/RX Yoshihiro Shimoda
2023-06-08 2:20 ` [PATCH net-next v4 1/2] net: renesas: rswitch: Use napi_gro_receive() in RX Yoshihiro Shimoda
2023-06-08 2:20 ` [PATCH net-next v4 2/2] net: renesas: rswitch: Use hardware pause features Yoshihiro Shimoda
2023-06-10 18:53 ` 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=168642322622.21298.7526575301146103242.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
--cc=simon.horman@corigine.com \
--cc=yoshihiro.shimoda.uh@renesas.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