From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
kernelxing@tencent.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/4] net: rps/rfs improvements
Date: Thu, 30 Mar 2023 12:00:18 +0000 [thread overview]
Message-ID: <168017761889.14481.3652625864507169315.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230328235021.1048163-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 28 Mar 2023 23:50:17 +0000 you wrote:
> Jason Xing attempted to optimize napi_schedule_rps() by avoiding
> unneeded NET_RX_SOFTIRQ raises: [1], [2]
>
> This is quite complex to implement properly. I chose to implement
> the idea, and added a similar optimization in ____napi_schedule()
>
> Overall, in an intensive RPC workload, with 32 TX/RX queues with RFS
> I was able to observe a ~10% reduction of NET_RX_SOFTIRQ
> invocations.
>
> [...]
Here is the summary with links:
- [net-next,1/4] net: napi_schedule_rps() cleanup
https://git.kernel.org/netdev/net-next/c/8fcb76b934da
- [net-next,2/4] net: add softnet_data.in_net_rx_action
https://git.kernel.org/netdev/net-next/c/c59647c0dc67
- [net-next,3/4] net: optimize napi_schedule_rps()
https://git.kernel.org/netdev/net-next/c/821eba962d95
- [net-next,4/4] net: optimize ____napi_schedule() to avoid extra NET_RX_SOFTIRQ
https://git.kernel.org/netdev/net-next/c/8b43fd3d1d7d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-30 12:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:50 [PATCH net-next 0/4] net: rps/rfs improvements Eric Dumazet
2023-03-28 23:50 ` [PATCH net-next 1/4] net: napi_schedule_rps() cleanup Eric Dumazet
2023-03-28 23:50 ` [PATCH net-next 2/4] net: add softnet_data.in_net_rx_action Eric Dumazet
2023-03-28 23:50 ` [PATCH net-next 3/4] net: optimize napi_schedule_rps() Eric Dumazet
2023-03-28 23:50 ` [PATCH net-next 4/4] net: optimize ____napi_schedule() to avoid extra NET_RX_SOFTIRQ Eric Dumazet
2023-03-29 12:47 ` Yunsheng Lin
2023-03-29 15:47 ` Eric Dumazet
2023-03-30 2:33 ` Yunsheng Lin
2023-03-30 2:57 ` Eric Dumazet
2023-03-30 6:47 ` Yunsheng Lin
2023-03-30 7:36 ` Yunsheng Lin
2023-03-30 9:50 ` Jason Xing
2023-03-30 11:39 ` Paolo Abeni
2023-03-30 11:44 ` Eric Dumazet
2023-03-30 12:03 ` Jason Xing
2023-03-29 2:40 ` [PATCH net-next 0/4] net: rps/rfs improvements Jason Xing
2023-03-30 3:04 ` Jakub Kicinski
2023-03-30 3:15 ` Eric Dumazet
2023-03-30 3:39 ` Eric Dumazet
2023-03-30 3:57 ` Jakub Kicinski
2023-03-30 12:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-29 13:17 Aiden Leong
2023-03-29 13:18 ` Aiden Leong
2023-03-29 15:33 ` Eric Dumazet
2023-03-29 16:21 ` Jason Xing
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=168017761889.14481.3652625864507169315.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).