From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: Yury Norov <yury.norov@gmail.com>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Dmitry Vyukov <dvyukov@google.com>,
Sander Vanheule <sander@svanheule.net>,
Alexey Klimov <klimov.linux@gmail.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v2 0/5] cpumask: cleanup nr_cpu_ids vs nr_cpumask_bits mess
Date: Tue, 6 Sep 2022 16:38:33 +0200 [thread overview]
Message-ID: <YxdbaWaO8lWWqT9q@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <xhsmhy1uwbtbc.mognet@vschneid.remote.csb>
On Tue, Sep 06, 2022 at 01:06:47PM +0100, Valentin Schneider wrote:
> #define nr_cpumask_bits nr_cpu_ids
That assumes the CPU space is dense; is this so? That is, you can have 4
CPUs while the highest cpu number is vastly larger than 4.
It's uncommon, but not unheard of I think. ISTR some BIOSes leaving
holes in the CPU space when there were empty CPU sockets on the
motherboard.
next prev parent reply other threads:[~2022-09-06 15:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 23:08 [PATCH v2 0/5] cpumask: cleanup nr_cpu_ids vs nr_cpumask_bits mess Yury Norov
2022-09-05 23:08 ` [PATCH v2 1/5] smp: don't declare nr_cpu_ids if NR_CPUS == 1 Yury Norov
2022-09-06 8:53 ` Peter Zijlstra
2022-09-06 14:06 ` Yury Norov
2022-09-06 14:36 ` Peter Zijlstra
2022-09-06 15:01 ` Andy Shevchenko
2022-09-06 17:53 ` Peter Zijlstra
2022-09-06 15:07 ` Yury Norov
2022-09-07 8:02 ` David Laight
2022-09-05 23:08 ` [PATCH v2 2/5] smp: add set_nr_cpu_ids() Yury Norov
2022-09-05 23:08 ` [PATCH v2 3/5] lib/cpumask: delete misleading comment Yury Norov
2022-09-05 23:08 ` [PATCH v2 4/5] lib/cpumask: deprecate nr_cpumask_bits Yury Norov
2022-09-05 23:08 ` [PATCH v2 5/5] lib/cpumask: add FORCE_NR_CPUS config option Yury Norov
2022-10-18 8:21 ` Geert Uytterhoeven
2022-10-18 13:15 ` Geert Uytterhoeven
2022-10-18 13:15 ` Geert Uytterhoeven
2022-10-18 13:41 ` Andreas Schwab
2022-10-18 13:41 ` Andreas Schwab
2022-10-18 13:50 ` Geert Uytterhoeven
2022-10-18 13:50 ` Geert Uytterhoeven
2022-10-18 14:35 ` Yury Norov
2022-10-18 14:35 ` Yury Norov
2022-10-18 14:44 ` Andy Shevchenko
2022-10-18 14:44 ` Andy Shevchenko
2022-10-18 14:59 ` Yury Norov
2022-10-18 14:59 ` Yury Norov
2022-10-18 15:15 ` Geert Uytterhoeven
2022-10-18 15:15 ` Geert Uytterhoeven
2022-10-18 16:16 ` Yury Norov
2022-10-18 16:16 ` Yury Norov
2022-10-19 6:58 ` Geert Uytterhoeven
2022-10-19 6:58 ` Geert Uytterhoeven
2022-09-06 8:55 ` [PATCH v2 0/5] cpumask: cleanup nr_cpu_ids vs nr_cpumask_bits mess Peter Zijlstra
2022-09-06 12:06 ` Valentin Schneider
2022-09-06 14:38 ` Peter Zijlstra [this message]
2022-09-06 15:45 ` Valentin Schneider
2022-09-06 16:26 ` Yury Norov
2022-09-06 14:48 ` Yury Norov
2022-09-06 14:35 ` Yury Norov
2022-09-15 14:45 ` Yury Norov
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=YxdbaWaO8lWWqT9q@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=klimov.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=paulmck@kernel.org \
--cc=sander@svanheule.net \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=vschneid@redhat.com \
--cc=yury.norov@gmail.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 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.