From: patchwork-bot+netdevbpf@kernel•org
To: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Cc: netdev@vger•kernel.org, linux-rt-devel@lists•linux.dev,
linux-ppp@vger•kernel.org, davem@davemloft•net,
andrew+netdev@lunn•ch, clrkwllms@kernel•org, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, horms@kernel•org,
rostedt@goodmis•org, tglx@linutronix•de, gnault@redhat•com
Subject: Re: [PATCH net-next v3 0/1] ppp: Replace per-CPU recursion counter with lock-owner field
Date: Thu, 17 Jul 2025 13:50:08 +0000 [thread overview]
Message-ID: <175276020851.1941871.13592848433216998317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715150806.700536-1-bigeasy@linutronix.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Tue, 15 Jul 2025 17:08:05 +0200 you wrote:
> This is another approach to avoid relying on local_bh_disable() for
> locking of per-CPU in ppp.
>
> I redid it with the per-CPU lock and local_lock_nested_bh() as discussed
> in v1. The xmit_recursion counter has been removed since it served the
> same purpose as the owner field. Both were updated and checked.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/1] ppp: Replace per-CPU recursion counter with lock-owner field
https://git.kernel.org/netdev/net-next/c/d4f6460a4bc5
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:[~2025-07-17 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 15:08 [PATCH net-next v3 0/1] ppp: Replace per-CPU recursion counter with lock-owner field Sebastian Andrzej Siewior
2025-07-15 15:08 ` [PATCH net-next v3 1/1] " Sebastian Andrzej Siewior
2025-07-15 17:37 ` [PATCH net-next v3 0/1] " Guillaume Nault
2025-07-17 13:40 ` Paolo Abeni
2025-07-17 13:50 ` 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=175276020851.1941871.13592848433216998317.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=bigeasy@linutronix$(echo .)de \
--cc=clrkwllms@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gnault@redhat$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=linux-rt-devel@lists$(echo .)linux.dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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