From: patchwork-bot+netdevbpf@kernel.org
To: Yan Zhai <yan@cloudflare.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jiri@resnulli.us,
horms@kernel.org, daniel@iogearbox.net, lorenzo@kernel.org,
lixiaoyan@google.com, weiwan@google.com, alexanderduyck@fb.com,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@cloudflare.com,
joel@joelfernandes.org, paulmck@kernel.org, toke@redhat.com,
alexei.starovoitov@gmail.com, rostedt@goodmis.org,
mark.rutland@arm.com, hawk@kernel.org, bigeasy@linutronix.de
Subject: Re: [PATCH v5 net 0/3] Report RCU QS for busy network kthreads
Date: Thu, 21 Mar 2024 04:40:27 +0000 [thread overview]
Message-ID: <171099602793.26207.3374009714899466289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1710877680.git.yan@cloudflare.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 19 Mar 2024 13:44:30 -0700 you wrote:
> This changeset fixes a common problem for busy networking kthreads.
> These threads, e.g. NAPI threads, typically will do:
>
> * polling a batch of packets
> * if there are more work, call cond_resched() to allow scheduling
> * continue to poll more packets when rx queue is not empty
>
> [...]
Here is the summary with links:
- [v5,net,1/3] rcu: add a helper to report consolidated flavor QS
https://git.kernel.org/netdev/net/c/1a77557d48cf
- [v5,net,2/3] net: report RCU QS on threaded NAPI repolling
https://git.kernel.org/netdev/net/c/d6dbbb11247c
- [v5,net,3/3] bpf: report RCU QS in cpumap kthread
https://git.kernel.org/netdev/net/c/00bf63122459
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:[~2024-03-21 4:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 20:44 [PATCH v5 net 0/3] Report RCU QS for busy network kthreads Yan Zhai
2024-03-19 20:44 ` [PATCH v5 net 1/3] rcu: add a helper to report consolidated flavor QS Yan Zhai
2024-03-19 21:31 ` Paul E. McKenney
2024-03-19 22:00 ` Yan Zhai
2024-03-19 22:08 ` Paul E. McKenney
2024-03-22 11:24 ` Sebastian Andrzej Siewior
2024-03-22 21:30 ` Paul E. McKenney
2024-03-23 2:02 ` Yan Zhai
2024-03-23 23:53 ` Paul E. McKenney
2024-04-05 13:49 ` Sebastian Andrzej Siewior
2024-04-05 18:13 ` Paul E. McKenney
2024-03-19 20:44 ` [PATCH v5 net 2/3] net: report RCU QS on threaded NAPI repolling Yan Zhai
2024-03-19 21:32 ` Paul E. McKenney
2024-03-19 20:44 ` [PATCH v5 net 3/3] bpf: report RCU QS in cpumap kthread Yan Zhai
2024-03-19 21:32 ` Paul E. McKenney
2024-03-20 10:30 ` [PATCH v5 net 0/3] Report RCU QS for busy network kthreads Jesper Dangaard Brouer
2024-03-21 4: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=171099602793.26207.3374009714899466289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=joel@joelfernandes.org \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=lorenzo@kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=toke@redhat.com \
--cc=weiwan@google.com \
--cc=yan@cloudflare.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).