From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xenproject.org
Subject: xentrace buffer size, maxcpus and online cpus
Date: Tue, 30 May 2023 09:58:59 +0200 [thread overview]
Message-ID: <20230530095859.60a3e4ea.olaf@aepfle.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
While looking again through calculate_tbuf_size after a very long time,
I was wondering why the code uses nr_cpu_ids instead of num_online_cpus.
In case Xen was booted with maxcpus=N, would it be safe to use N as
upper limit? I think this would increase the per-cpu buffer size for
each active pcpu, and as a result more events could be captured.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-05-30 7:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 7:58 Olaf Hering [this message]
2023-05-30 8:41 ` xentrace buffer size, maxcpus and online cpus Jan Beulich
2023-05-30 20:06 ` Olaf Hering
2023-05-31 9:05 ` Jan Beulich
2023-06-16 11:47 ` Olaf Hering
2023-06-16 11:52 ` Jan Beulich
2023-06-16 14:22 ` George Dunlap
2023-06-16 15:37 ` Olaf Hering
2023-06-16 16:08 ` Andrew Cooper
2023-06-19 10:16 ` Olaf Hering
2023-06-19 11:14 ` Andrew Cooper
2023-06-19 10:13 ` Olaf Hering
2023-06-19 10:22 ` Jan Beulich
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=20230530095859.60a3e4ea.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.