From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Discontig-devel] [PATCH] another discontig patch
Date: Wed, 16 Jul 2003 19:40:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105838466129009@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105618641519753@msgid-missing>
On Wed, Jul 16, 2003 at 12:29:52PM -0700, Jesse Barnes wrote:
> @@ -210,8 +210,8 @@
> system with an A0 or A1 stepping CPU.
>
> config NUMA
> - bool "Enable NUMA support" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
> - default y if IA64_SGI_SN2
> + bool
> + default y if IA64_SGI_SN2 || IA64_GENERIC
> help
> Say Y to compile the kernel to support NUMA (Non-Uniform Memory
> Access). This option is for configuring high-end multiprocessor
If you're removing the question, you can remove the helptext too.
> @@ -235,8 +235,7 @@
>
> config DISCONTIGMEM
> bool
> - depends on IA64_SGI_SN2 || (IA64_GENERIC || IA64_DIG || IA64_HP_ZX1) && NUMA
> - default y
> + default y if IA64_SGI_SN2 || IA64_GENERIC
> help
> Say Y to support efficient handling of discontiguous physical memory,
> for architectures which are either NUMA (Non-Uniform Memory Access)
This one already shouldn't have helptext ;-)
> - * on a BANKSIZE boundary. Multiple banks per node is not supported.
> + * on a GRANULE boundary. Multiple banks per node is not supported.
Multiple banks *are* not supported ;-) The feature of multiple banks
*is* not supported.
> @@ -22,15 +22,17 @@
>
> struct pglist_data;
> struct ia64_node_data {
> - short active_cpu_count;
> short node;
> + short active_cpu_count;
> + /*
> + * The fields are read-only (after boot). They contain pointers to various structures
> + * located on other nodes. Ths data is replicated on each node in order to reduce
> + * off-node references.
> + */
Can you wrap comments at 80 columns? It makes them much easier to read.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-07-16 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 9:06 [Discontig-devel] [PATCH] another discontig patch Christoph Hellwig
2003-06-21 14:48 ` Martin J. Bligh
2003-06-22 5:53 ` Jesse Barnes
2003-06-22 5:57 ` Jesse Barnes
2003-06-22 15:25 ` Martin J. Bligh
2003-06-23 17:20 ` William Lee Irwin III
2003-07-16 19:29 ` Jesse Barnes
2003-07-16 19:40 ` Matthew Wilcox [this message]
2003-07-16 19:51 ` Jesse Barnes
2003-07-16 19:56 ` Erich Focht
2003-07-16 22:37 ` Jesse Barnes
2003-07-17 8:23 ` Erich Focht
2003-07-18 0:16 ` Jesse Barnes
2003-07-18 16:15 ` Erich Focht
2003-07-21 18:46 ` Takayoshi Kochi
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=marc-linux-ia64-105838466129009@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@vger.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