mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, tj@kernel.org,
	akpm@linux-foundation.org, shuah@kernel.org, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	gustavold@gmail.com, usamaarif642@gmail.com,
	linux-kselftest@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v3 0/4] netconsole: Optimize console registration and improve testing
Date: Tue, 10 Jun 2025 21:40:34 +0000	[thread overview]
Message-ID: <174959163475.2619474.7924574005472646166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250609-netcons_ext-v3-0-5336fa670326@debian.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 09 Jun 2025 02:46:25 -0700 you wrote:
> During performance analysis of console subsystem latency, I discovered that
> netconsole registers console handlers even when no active targets exist.
> These orphaned console handlers are invoked on every printk() call, get
> the lock, iterate through empty target lists, and consume CPU cycles
> without performing any useful work.
> 
> This patch series addresses the inefficiency by:
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/4] netconsole: Only register console drivers when targets are configured
    https://git.kernel.org/netdev/net-next/c/bc0cb64db1c7
  - [net-next,v3,2/4] netconsole: Add automatic console unregistration on target removal
    https://git.kernel.org/netdev/net-next/c/e99d938f8671
  - [net-next,v3,3/4] selftests: netconsole: Do not exit from inside the validation function
    https://git.kernel.org/netdev/net-next/c/69b25dd20c83
  - [net-next,v3,4/4] selftests: netconsole: Add support for basic netconsole target format
    https://git.kernel.org/netdev/net-next/c/224a6e602fb3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-06-10 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09  9:46 Breno Leitao
2025-06-09  9:46 ` [PATCH net-next v3 1/4] netconsole: Only register console drivers when targets are configured Breno Leitao
2025-06-09  9:46 ` [PATCH net-next v3 2/4] netconsole: Add automatic console unregistration on target removal Breno Leitao
2025-06-09  9:46 ` [PATCH net-next v3 3/4] selftests: netconsole: Do not exit from inside the validation function Breno Leitao
2025-06-09  9:46 ` [PATCH net-next v3 4/4] selftests: netconsole: Add support for basic netconsole target format Breno Leitao
2025-06-10 21: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=174959163475.2619474.7924574005472646166.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gustavold@gmail.com \
    --cc=horms@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tj@kernel.org \
    --cc=usamaarif642@gmail.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

all inboxes | Powered by JetHome®