From: Petr Mladek <pmladek@suse.com>
To: Breno Leitao <leitao@debian.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
horms@kernel.org, efault@gmx.de, john.ogness@linutronix.de,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
calvin@wbinvd.org, asml.silence@gmail.com, kernel-team@meta.com,
gustavold@gmail.com, asantostc@gmail.com
Subject: Re: [PATCH RFC net-next 1/2] netconsole: extract message fragmentation into write_msg_target()
Date: Mon, 24 Nov 2025 14:08:36 +0100 [thread overview]
Message-ID: <aSRY1AI7zDF-h-A9@pathway.suse.cz> (raw)
In-Reply-To: <20251121-nbcon-v1-1-503d17b2b4af@debian.org>
On Fri 2025-11-21 03:26:07, Breno Leitao wrote:
> Refactor the message fragmentation logic in write_msg() by extracting it
> into a separate write_msg_target() helper function. This makes the code
> more maintainable and prepares for future reuse in nbcon support for
> non-extended consoles.
>
> The helper function takes a target, message, and length, then handles
> splitting the message into MAX_PRINT_CHUNK-sized fragments for sending
> via send_udp().
>
> No functional change intended.
> --- a/drivers/net/netconsole.c
> +++ b/drivers/net/netconsole.c
> @@ -1559,6 +1559,20 @@ static void append_release(char *buf)
> scnprintf(buf, MAX_PRINT_CHUNK, "%s,", release);
> }
>
> +static void write_msg_target(struct netconsole_target *nt, const char *msg,
> + unsigned int len)
> +{
> + const char *tmp = msg;
> + int frag, left = len;
> +
> + while (left > 0) {
> + frag = min(left, MAX_PRINT_CHUNK);
> + send_udp(nt, tmp, frag);
> + tmp += frag;
> + left -= frag;
> + }
> +}
> +
> static void send_fragmented_body(struct netconsole_target *nt,
> const char *msgbody, int header_len,
> int msgbody_len, int extradata_len)
> @@ -1748,13 +1760,7 @@ static void write_msg(struct console *con, const char *msg, unsigned int len)
> * at least one target if we die inside here, instead
> * of unnecessarily keeping all targets in lock-step.
> */
> - tmp = msg;
> - for (left = len; left;) {
> - frag = min(left, MAX_PRINT_CHUNK);
> - send_udp(nt, tmp, frag);
> - tmp += frag;
> - left -= frag;
> - }
> + write_msg_target(nt, msg, len);
I would call the new function send_msg_udp() to make it symetric with:
static void write_ext_msg(struct console *con, const char *msg,
unsigned int len)
{
[...]
send_ext_msg_udp(nt, msg, len);
[...]
}
By other words, use "write_*()" when struct console * is passed
and send_*_udp() when struct netconsole_target * is passed.
The inconsistence confused me... ;-)
Note that write_msg()/write_ext_msg() are cut&pasted.
The only difference would be send_msg_udp()/send_ext_msg_udp().
> }
> }
> spin_unlock_irqrestore(&target_list_lock, flags);
Otherwise, I confirm that it is just a refactoring with no
functional change.
Feel free to use, ideally after the renaming function:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2025-11-24 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 11:26 [PATCH RFC net-next 0/2] netconsole: NBCON Infrastructure Support Breno Leitao
2025-11-21 11:26 ` [PATCH RFC net-next 1/2] netconsole: extract message fragmentation into write_msg_target() Breno Leitao
2025-11-24 13:08 ` Petr Mladek [this message]
2025-11-21 11:26 ` [PATCH RFC net-next 2/2] netconsole: add CONFIG_NETCONSOLE_NBCON for nbcon support Breno Leitao
2025-11-24 13:55 ` Petr Mladek
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=aSRY1AI7zDF-h-A9@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=asml.silence@gmail.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=efault@gmx.de \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).