[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250210-crafty-snobbish-pogona-83e904@leitao>
Date: Mon, 10 Feb 2025 03:07:24 -0800
From: Breno Leitao <leitao@...ian.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
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 net-next v5 8/8] netconsole: docs: Add documentation for
CPU number auto-population
Hello Bagas,
On Fri, Feb 07, 2025 at 08:50:22AM +0700, Bagas Sanjaya wrote:
> On Thu, Feb 06, 2025 at 03:05:59AM -0800, Breno Leitao wrote:
> > +.. note::
> > +
> > + If the user has set a conflicting `cpu` key in the userdata dictionary,
> > + both keys will be reported, with the kernel-populated entry appearing after
> > + the user one. For example::
>
> In that case, shouldn't the kernel autopopulates numbers of the rest of
> CPUs?
Do you mean listing all the CPUs that are *not* sending the current
message?
Let me come up with an example to try to understand this better. Let's
suppopse I have a machine with 64 cores, and cpu=42 is sending that
current message, then I would see the following on the dictionary:
cpu=42
You are suggesting we send all the other cpus, except 42 in a "key"?
Thanks
--breno
Powered by blists - more mailing lists