From: patchwork-bot+netdevbpf@kernel.org
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, torvalds@linuxfoundation.org,
x86@kernel.org, wangyang.guo@intel.com, arjan@linux.intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, will@kernel.org,
peterz@infradead.org, boqun.feng@gmail.com, mark.rutland@arm.com,
maz@kernel.org, qiuxu.zhuo@intel.com
Subject: Re: [patch V3 0/4] net, refcount: Address dst_entry reference count scalability issues
Date: Wed, 29 Mar 2023 02:30:19 +0000 [thread overview]
Message-ID: <168005701914.27658.17147408850533748612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230323102649.764958589@linutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Mar 2023 21:55:27 +0100 (CET) you wrote:
> Hi!
>
> This is version 3 of this series. Version 2 can be found here:
>
> https://lore.kernel.org/lkml/20230307125358.772287565@linutronix.de
>
> Wangyang and Arjan reported a bottleneck in the networking code related to
> struct dst_entry::__refcnt. Performance tanks massively when concurrency on
> a dst_entry increases.
>
> [...]
Here is the summary with links:
- [V3,1/4,V2,1/4] net: dst: Prevent false sharing vs. dst_entry:: __refcnt
https://git.kernel.org/netdev/net-next/c/d288a162dd1c
- [V3,2/4] atomics: Provide atomic_add_negative() variants
https://git.kernel.org/netdev/net-next/c/e5ab9eff46b0
- [V3,3/4] atomics: Provide rcuref - scalable reference counting
https://git.kernel.org/netdev/net-next/c/ee1ee6db0779
- [V3,4/4] net: dst: Switch to rcuref_t reference counting
https://git.kernel.org/netdev/net-next/c/bc9d3a9f2afc
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-29 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 20:55 [patch V3 0/4] net, refcount: Address dst_entry reference count scalability issues Thomas Gleixner
2023-03-23 20:55 ` [patch V3 1/4] [patch V2 1/4] net: dst: Prevent false sharing vs. dst_entry:: __refcnt Thomas Gleixner
2023-03-23 20:55 ` [patch V3 2/4] atomics: Provide atomic_add_negative() variants Thomas Gleixner
2023-03-23 20:55 ` [patch V3 3/4] atomics: Provide rcuref - scalable reference counting Thomas Gleixner
2023-03-23 20:55 ` [patch V3 4/4] net: dst: Switch to rcuref_t " Thomas Gleixner
2023-03-23 21:54 ` Linus Torvalds
2023-03-28 8:45 ` [patch V3 0/4] net, refcount: Address dst_entry reference count scalability issues Peter Zijlstra
2023-03-29 2:30 ` patchwork-bot+netdevbpf [this message]
2023-04-10 22:53 ` Paul E. McKenney
2023-04-17 11:44 ` Leon Romanovsky
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=168005701914.27658.17147408850533748612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arjan@linux.intel.com \
--cc=boqun.feng@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=qiuxu.zhuo@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.org \
--cc=wangyang.guo@intel.com \
--cc=will@kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).