From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: [patch] MAX_NR_NODES name change
Date: Wed, 31 Jul 2002 17:12:31 -0700 [thread overview]
Message-ID: <3D487CEF.5000107@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
This patch changes MAX_NR_NODES to be NR_NODES, so as to be more consistent
with the naming of NR_CPUS. It is easier to change this one as it only appears
in 3 places and NR_CPUS appears all over the place.
Cheers!
-Matt
[-- Attachment #2: max_nr_node-fix.patch --]
[-- Type: text/plain, Size: 1181 bytes --]
diff -Nur linux-2.5.29-vanilla/include/linux/mmzone.h linux-2.5.29-patched/include/linux/mmzone.h
--- linux-2.5.29-vanilla/include/linux/mmzone.h Fri Jul 26 19:58:25 2002
+++ linux-2.5.29-patched/include/linux/mmzone.h Wed Jul 31 17:09:20 2002
@@ -167,14 +167,14 @@
#define NODE_DATA(nid) (&contig_page_data)
#define NODE_MEM_MAP(nid) mem_map
-#define MAX_NR_NODES 1
+#define NR_NODES 1
#else /* !CONFIG_DISCONTIGMEM */
#include <asm/mmzone.h>
/* page->zone is currently 8 bits ... */
-#define MAX_NR_NODES (255 / MAX_NR_ZONES)
+#define NR_NODES (255 / MAX_NR_ZONES)
#endif /* !CONFIG_DISCONTIGMEM */
diff -Nur linux-2.5.29-vanilla/mm/page_alloc.c linux-2.5.29-patched/mm/page_alloc.c
--- linux-2.5.29-vanilla/mm/page_alloc.c Fri Jul 26 19:58:27 2002
+++ linux-2.5.29-patched/mm/page_alloc.c Wed Jul 31 17:09:00 2002
@@ -34,7 +34,7 @@
* Used by page_zone() to look up the address of the struct zone whose
* id is encoded in the upper bits of page->flags
*/
-zone_t *zone_table[MAX_NR_ZONES*MAX_NR_NODES];
+zone_t *zone_table[MAX_NR_ZONES*NR_NODES];
EXPORT_SYMBOL(zone_table);
static char *zone_names[MAX_NR_ZONES] = { "DMA", "Normal", "HighMem" };
reply other threads:[~2002-08-01 0:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D487CEF.5000107@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=linux-kernel@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