[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d441f627-1686-40fa-80cb-e84c590b8b02@lunn.ch>
Date: Fri, 24 Jan 2025 17:02:26 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Jonathan Corbet <corbet@....net>,
Shuah Khan <shuah@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kselftest@...r.kernel.org, rdunlap@...radead.org,
kernel-team@...a.com
Subject: Re: [PATCH RFC net-next v3 0/8] netconsole: Add support for CPU
population
On Fri, Jan 24, 2025 at 07:16:39AM -0800, Breno Leitao wrote:
> The current implementation of netconsole sends all log messages in
> parallel, which can lead to an intermixed and interleaved output on the
> receiving side. This makes it challenging to demultiplex the messages
> and attribute them to their originating CPUs.
>
> As a result, users and developers often struggle to effectively analyze
> and debug the parallel log output received through netconsole.
I know very little about consoles and netconsle, so this is probably a
silly question:
Why is this a netconsole problem, and not a generic console problem?
Can other console types also send in parallel? Do they have the same
issue of intermixing?
Andrew
Powered by blists - more mailing lists