linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [patch 02/10] powerpc: Move CONFIG_PPC64 into CPU selection
Date: Wed, 13 Jun 2007 06:57:41 +0200	[thread overview]
Message-ID: <946b0ffac20f415fdde286061daad572@kernel.crashing.org> (raw)
In-Reply-To: <18031.15747.57370.99388@cargo.ozlabs.ibm.com>

>> It would be good to converge the 32- and 64-bit implementations,
>> and/or allow a single kernel image to work on both 32-bit and
>> 64-bit systems,  The current situation is far removed from that,
>> so this patch is a bit premature in that aspect.
>
> There will always be differences in emphasis and focus between 32-bit
> and 64-bit.  For example, the vast majority of 32-bit systems are UP,
> with a few 2-way SMP systems, an insignificant number of 4-way
> systems, and nothing bigger than 4-way.  In contrast, most 64-bit
> machines are SMP, with enough large SMP machines (64-way and bigger)
> to be worth worrying about.  Hence the 64-bit code focuses on SMP
> scalability whereas the 32-bit code focuses on performance for UP and
> 2-way systems - which is why the hash table invalidations get batched
> up on 64-bit machines but not on 32-bit machines, for instance.
> Similarly, 64-bit supports large memory (>4GB) and NUMA machines,
> whereas 32-bit doesn't.

While all this is certainly true, there still are many
differences between 32-bit and 64-bit that aren't really
warranted.  Also, things like the scalability "knobs"
should perhaps not be directly keyed of the PPC64 symbol.

Anyway, nothing to worry about now I guess ;-)


Segher

  reply	other threads:[~2007-06-13  4:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 23:28 [patch 00/10] CPU selection Kconfig cleanup, take 2 arnd
2007-06-11 23:28 ` [patch 01/10] powerpc: split out CPU specific options into a new Kconfig file arnd
2007-06-12  4:02   ` Stephen Rothwell
2007-06-12  7:42     ` Arnd Bergmann
2007-06-12 11:12       ` Paul Mackerras
2007-06-12 12:42         ` Arnd Bergmann
2007-06-11 23:28 ` [patch 02/10] powerpc: Move CONFIG_PPC64 into CPU selection arnd
2007-06-12  6:33   ` Paul Mackerras
2007-06-12  8:08     ` Arnd Bergmann
2007-06-12 11:11       ` Paul Mackerras
2007-06-12 11:35         ` Segher Boessenkool
2007-06-12 21:32           ` Benjamin Herrenschmidt
2007-06-13  4:52             ` Segher Boessenkool
2007-06-13  0:42           ` Paul Mackerras
2007-06-13  4:57             ` Segher Boessenkool [this message]
2007-06-12 11:49         ` Arnd Bergmann
2007-06-11 23:28 ` [patch 03/10] powerpc: move 82xx/83xx/86xx Kconfig options to platform selection arnd
2007-06-11 23:28 ` [patch 04/10] powerpc: rename add_bridge to avoid namespace clashes arnd
2007-06-12  4:11   ` Stephen Rothwell
2007-06-11 23:28 ` [patch 05/10] powerpc: Multiplatformize 8{2,3,6}xx configuration arnd
2007-06-11 23:28 ` [patch 06/10] powerpc: multiplatformize embedded6xx Kconfig arnd
2007-06-12  4:15   ` Stephen Rothwell
2007-06-12  4:16     ` Stephen Rothwell
2007-06-12  5:59   ` Kumar Gala
2007-06-12  7:46     ` Arnd Bergmann
2007-06-11 23:28 ` [patch 07/10] powerpc: multiplatformize 52xx configuration arnd
2007-06-11 23:28 ` [patch 08/10] powerpc: multiplatformize 85xx Kconfig arnd
2007-06-11 23:28 ` [patch 09/10] powerpc: autoselect PPC_MULTIPLATFORM arnd
2007-06-11 23:28 ` [patch 10/10] powerpc: autoselect optimal -mcpu= flag by platform arnd

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=946b0ffac20f415fdde286061daad572@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).