From: Christoph Lameter <clameter@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Christoph Hellwig <hch@infradead.org>,
Marcelo Tosatti <marcelo@kvack.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Bligh <mbligh@google.com>,
Christoph Lameter <clameter@sgi.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andi Kleen <ak@suse.de>
Subject: [RFC 8/8] Optimize mempolicies for a single zone
Date: Fri, 7 Jul 2006 17:05:43 -0700 (PDT) [thread overview]
Message-ID: <20060708000543.3829.24370.sendpatchset@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060708000501.3829.25578.sendpatchset@schroedinger.engr.sgi.com>
Use SINGLE_ZONE to remove the highest zone determination
Siged-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.17-mm6/mm/mempolicy.c
===================================================================
--- linux-2.6.17-mm6.orig/mm/mempolicy.c 2006-07-07 16:50:18.790221361 -0700
+++ linux-2.6.17-mm6/mm/mempolicy.c 2006-07-07 16:53:46.057679926 -0700
@@ -103,9 +103,11 @@ static struct kmem_cache *sn_cache;
#define PDprintk(fmt...)
+#ifndef SINGLE_ZONE
/* Highest zone. An specific allocation for a zone below that is not
policied. */
int policy_zone = 0;
+#endif
struct mempolicy default_policy = {
.refcnt = ATOMIC_INIT(1), /* never free it */
Index: linux-2.6.17-mm6/include/linux/mempolicy.h
===================================================================
--- linux-2.6.17-mm6.orig/include/linux/mempolicy.h 2006-07-03 13:47:21.727467854 -0700
+++ linux-2.6.17-mm6/include/linux/mempolicy.h 2006-07-07 16:53:46.057679926 -0700
@@ -162,12 +162,18 @@ extern struct zonelist *huge_zonelist(st
unsigned long addr);
extern unsigned slab_node(struct mempolicy *policy);
+#ifndef SINGLE_ZONE
+#define policy_zone ZONE_NORMAL
+#else
extern int policy_zone;
+#endif
static inline void check_highest_zone(int k)
{
+#ifndef SINGLE_ZONE
if (k > policy_zone)
policy_zone = k;
+#endif
}
int do_migrate_pages(struct mm_struct *mm,
next prev parent reply other threads:[~2006-07-08 0:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 0:05 [RFC 0/8] Optional ZONE_DMA Christoph Lameter
2006-07-08 0:05 ` [RFC 1/8] Add CONFIG_ZONE_DMA to all archesM Christoph Lameter
2006-07-10 0:52 ` KAMEZAWA Hiroyuki
2006-07-10 15:56 ` Christoph Lameter
2006-07-11 7:11 ` KAMEZAWA Hiroyuki
2006-07-08 0:05 ` [RFC 2/8] slab allocator: Make DMA support configurable Christoph Lameter
2006-07-08 0:05 ` [RFC 3/8] eventcounters: Optional ZONE_DMA Christoph Lameter
2006-07-08 0:05 ` [RFC 4/8] page allocator: " Christoph Lameter
2006-07-08 0:23 ` Andi Kleen
2006-07-08 0:41 ` Christoph Lameter
2006-07-08 0:05 ` [RFC 5/8] x86_64 without ZONE_DMA Christoph Lameter
2006-07-08 0:20 ` Andi Kleen
2006-07-08 0:42 ` Christoph Lameter
2006-07-08 1:00 ` Andi Kleen
2006-07-08 1:25 ` Christoph Lameter
2006-07-08 0:05 ` [RFC 6/8] i386 " Christoph Lameter
2006-07-08 0:05 ` [RFC 7/8] Single zone optimizations Christoph Lameter
2006-07-08 0:19 ` Andi Kleen
2006-07-08 0:05 ` Christoph Lameter [this message]
2006-07-08 0:17 ` [RFC 8/8] Optimize mempolicies for a single zone Andi Kleen
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=20060708000543.3829.24370.sendpatchset@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=mbligh@google.com \
--cc=nickpiggin@yahoo.com.au \
/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
Powered by JetHome