From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
rdunlap@infradead.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v5 8/8] netconsole: docs: Add documentation for CPU number auto-population
Date: Tue, 11 Feb 2025 06:42:51 +0700 [thread overview]
Message-ID: <Z6qO-_Ebnn5OTkgy@archie.me> (raw)
In-Reply-To: <20250210-crafty-snobbish-pogona-83e904@leitao>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On Mon, Feb 10, 2025 at 03:07:24AM -0800, Breno Leitao wrote:
> 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?
Nope.
>
> 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"?
Sort of.
I mean, on the dictionary, we would see user-defined cpu number on one cpu,
and kernel-generated numbers on the rest.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-10 23:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 11:05 [PATCH net-next v5 0/8] netconsole: Add support for CPU population Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 1/8] netconsole: consolidate send buffers into netconsole_target struct Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 2/8] netconsole: Rename userdata to extradata Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 3/8] netconsole: Helper to count number of used entries Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 4/8] netconsole: Introduce configfs helpers for sysdata features Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 5/8] netconsole: Include sysdata in extradata entry count Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 6/8] netconsole: add support for sysdata and CPU population Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 7/8] netconsole: selftest: test for sysdata CPU Breno Leitao
2025-02-06 11:05 ` [PATCH net-next v5 8/8] netconsole: docs: Add documentation for CPU number auto-population Breno Leitao
2025-02-07 1:50 ` Bagas Sanjaya
2025-02-10 11:07 ` Breno Leitao
2025-02-10 23:42 ` Bagas Sanjaya [this message]
2025-02-10 15:10 ` [PATCH net-next v5 0/8] netconsole: Add support for CPU population patchwork-bot+netdevbpf
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=Z6qO-_Ebnn5OTkgy@archie.me \
--to=bagasdotme@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
/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®