public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@linuxcare.com.au>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH]: Only one memory zone for sparc64
Date: Thu, 15 Mar 2001 19:13:52 +1100	[thread overview]
Message-ID: <20010315191352.D1598@linuxcare.com> (raw)


Hi,

On sparc64 we dont care about the different memory zones and iterating
through them all over the place only serves to waste CPU. I suspect this
would be the case with some other architectures but for the moment I
have just enabled it for sparc64.

With this patch I get close to a 1% improvement in dbench on the dual
ultra60.

Anton

diff -ru linux/include/linux/mmzone.h linux_work/include/linux/mmzone.h
--- linux/include/linux/mmzone.h	Thu Mar 15 19:03:47 2001
+++ linux_work/include/linux/mmzone.h	Tue Mar 13 18:46:59 2001
@@ -63,7 +63,19 @@
 #define ZONE_DMA		0
 #define ZONE_NORMAL		1
 #define ZONE_HIGHMEM		2
+#ifdef __sparc_v9__
+#define MAX_NR_ZONES		1
+#define ZONE_NAMES		{ "DMA" }
+#define ZONE_BALANCE_RATIO	{ 32 }
+#define ZONE_BALANCE_MIN	{ 10 }
+#define ZONE_BALANCE_MAX	{ 255 }
+#else
 #define MAX_NR_ZONES		3
+#define ZONE_NAMES		{ "DMA", "Normal", "HighMem" }
+#define ZONE_BALANCE_RATIO	{ 32, 128, 128 }
+#define ZONE_BALANCE_MIN	{ 10, 10, 10 }
+#define ZONE_BALANCE_MAX	{ 255, 255, 255 }
+#endif
 
 /*
  * One allocation request operates on a zonelist. A zonelist
diff -ru linux/mm/page_alloc.c linux_work/mm/page_alloc.c
--- linux/mm/page_alloc.c	Mon Mar 12 13:33:02 2001
+++ linux_work/mm/page_alloc.c	Mon Mar 12 13:00:08 2001
@@ -23,10 +23,10 @@
 int nr_inactive_dirty_pages;
 pg_data_t *pgdat_list;
 
-static char *zone_names[MAX_NR_ZONES] = { "DMA", "Normal", "HighMem" };
-static int zone_balance_ratio[MAX_NR_ZONES] = { 32, 128, 128, };
-static int zone_balance_min[MAX_NR_ZONES] = { 10 , 10, 10, };
-static int zone_balance_max[MAX_NR_ZONES] = { 255 , 255, 255, };
+static char *zone_names[MAX_NR_ZONES] = ZONE_NAMES;
+static int zone_balance_ratio[MAX_NR_ZONES] = ZONE_BALANCE_RATIO;
+static int zone_balance_min[MAX_NR_ZONES] = ZONE_BALANCE_MIN;
+static int zone_balance_max[MAX_NR_ZONES] = ZONE_BALANCE_MAX;
 
 struct list_head active_list;
 struct list_head inactive_dirty_list;

             reply	other threads:[~2001-03-15  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  8:13 Anton Blanchard [this message]
2001-03-15 12:36 ` [PATCH]: Only one memory zone for sparc64 Rik van Riel
2001-03-16 12:16 ` Stephen C. Tweedie
2001-03-17  2:45   ` Anton Blanchard

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=20010315191352.D1598@linuxcare.com \
    --to=anton@linuxcare.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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