From: Jakub Kicinski <kuba@kernel•org>
To: Breno Leitao <leitao@debian•org>
Cc: Petr Mladek <pmladek@suse•com>,
Andrew Lunn <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Shuah Khan <shuah@kernel•org>,
Simon Horman <horms@kernel•org>, Jonathan Corbet <corbet@lwn•net>,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-kselftest@vger•kernel.org, linux-doc@vger•kernel.org,
gustavold@gmail•com, asantostc@gmail•com, calvin@wbinvd•org,
kernel-team@meta•com, davej@codemonkey•org.uk
Subject: Re: [PATCH net-next 0/4] (no cover subject)
Date: Tue, 9 Dec 2025 16:37:45 +0900 [thread overview]
Message-ID: <20251209163745.3d0fcdfe@kernel.org> (raw)
In-Reply-To: <7jdruzcpkeyhuudwi6uzg2vsc5mhgpq7qz4ym7vqqmgs7j3524@cvtnzneddg2d>
On Fri, 5 Dec 2025 02:21:08 -0800 Breno Leitao wrote:
> 1) Have a binary in each machine:
> 2) Send a ping directly to the console
> 3) Using per-loglevel patchset.
> 4) send messages only to netconsole (this patchset)
I think I was alluding that another option (not saying that it's the
best but IIUC your requirements it'd be the best fit)):
5) Add a keepalive configfs knob, if set to a non-zero value netconsole
will send an empty (?) message at given interval
Pros:
- truly does not require a user binary to run periodically, netcons
would set a timer in the kernel
Cons:
- does not provide the arbitrary "console bypass" message
functionality
next prev parent reply other threads:[~2025-12-09 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 14:20 [PATCH net-next 0/4] (no cover subject) Breno Leitao
2025-11-28 14:20 ` [PATCH net-next 1/4] netconsole: extract message fragmentation into send_msg_udp() Breno Leitao
2025-11-30 15:32 ` Simon Horman
2025-11-28 14:20 ` [PATCH net-next 2/4] netconsole: Add configfs attribute for direct message sending Breno Leitao
2025-11-30 15:32 ` Simon Horman
2025-11-28 14:20 ` [PATCH net-next 3/4] selftests/netconsole: Switch to configfs send_msg interface Breno Leitao
2025-11-30 15:32 ` Simon Horman
2025-11-28 14:20 ` [PATCH net-next 4/4] Documentation: netconsole: Document send_msg configfs attribute Breno Leitao
2025-11-30 15:32 ` Simon Horman
2025-11-30 15:34 ` [PATCH net-next 0/4] (no cover subject) Simon Horman
2025-12-02 0:36 ` Jakub Kicinski
2025-12-02 10:18 ` Breno Leitao
2025-12-02 18:24 ` Jakub Kicinski
2025-12-04 10:46 ` Petr Mladek
2025-12-04 10:51 ` Petr Mladek
2025-12-05 10:21 ` Breno Leitao
2025-12-08 14:52 ` Petr Mladek
2025-12-09 17:36 ` Breno Leitao
2025-12-09 7:37 ` Jakub Kicinski [this message]
2025-12-09 17:46 ` Breno Leitao
2025-12-10 4:05 ` Jakub Kicinski
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=20251209163745.3d0fcdfe@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=asantostc@gmail$(echo .)com \
--cc=calvin@wbinvd$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=davej@codemonkey$(echo .)org.uk \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gustavold@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kernel-team@meta$(echo .)com \
--cc=leitao@debian$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pmladek@suse$(echo .)com \
--cc=shuah@kernel$(echo .)org \
/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