From: David Laight <David.Laight@ACULAB.COM>
To: 'Peter Zijlstra' <peterz@infradead.org>,
Yury Norov <yury.norov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <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>,
"Valentin Schneider" <vschneid@redhat.com>,
Sander Vanheule <sander@svanheule.net>,
Alexey Klimov <klimov.linux@gmail.com>,
Eric Biggers <ebiggers@google.com>
Subject: RE: [PATCH v2 1/5] smp: don't declare nr_cpu_ids if NR_CPUS == 1
Date: Wed, 7 Sep 2022 08:02:42 +0000 [thread overview]
Message-ID: <61fb5bada0be421abddc871908f8a3dd@AcuMS.aculab.com> (raw)
In-Reply-To: <Yxda9/XP85D1sR39@hirez.programming.kicks-ass.net>
From: Peter Zijlstra
> Sent: 06 September 2022 15:37
...
> It was suggested the other day we remove a whole bunch of SMP=n code and
> unconditionally use SMP code, even if its pointless on UP just to make
> the source simpler.
All the world isn't x86.
There are some small embedded systems which are definitely UP
and where you don't want any of the SMP 'bloat'.
Architectures like NiosII will only ever be SMP.
There certainly have recently been (and probably still are)
small ppc cpu for embedded systems that are UP.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-09-07 8:03 UTC|newest]
Thread overview: 31+ 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 [this message]
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:41 ` Andreas Schwab
2022-10-18 13:50 ` Geert Uytterhoeven
2022-10-18 14:35 ` Yury Norov
2022-10-18 14:44 ` Andy Shevchenko
2022-10-18 14:59 ` Yury Norov
2022-10-18 15:15 ` Geert Uytterhoeven
2022-10-18 16:16 ` Yury Norov
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
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=61fb5bada0be421abddc871908f8a3dd@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--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=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox