From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, Mel Gorman <mel@csn.ul.ie>,
stable@kernel.org, Linux Memory Management <linux-mm@kvack.org>
Subject: [PATCH 1/2] zone allow unaligned zone boundaries add configuration
Date: Mon, 22 May 2006 10:53:11 +0100 [thread overview]
Message-ID: <20060522095311.GA6869@shadowen.org> (raw)
In-Reply-To: <exportbomb.1148291574@pinky>
zone allow unaligned zone boundaries add configuration
Add a configuration definition for UNALIGNED_ZONE_BOUNDARIES. Default
to on unless the architecture indicates that it ensures that the boundaries
are correctly aligned.
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
---
Kconfig | 13 +++++++++++++
1 files changed, 13 insertions(+)
diff -upN reference/mm/Kconfig current/mm/Kconfig
--- reference/mm/Kconfig
+++ current/mm/Kconfig
@@ -145,3 +145,16 @@ config MIGRATION
while the virtual addresses are not changed. This is useful for
example on NUMA systems to put pages nearer to the processors accessing
the page.
+
+#
+# Support for buddy zone boundaries within a MAX_ORDER sized area.
+#
+config UNALIGNED_ZONE_BOUNDARIES
+ bool "Unaligned zone boundaries"
+ default n if ARCH_ALIGNED_ZONE_BOUNDARIES
+ default y
+ help
+ Adds checks to the buddy allocator to ensure we do not
+ coalesce buddies across zone boundaries. The default
+ should be correct for your architecture. Enable this if
+ you are having trouble and you are requested to in dmesg.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-05-22 9:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 8:22 [patch 1/2] mm: detect bad zones Nick Piggin
2006-05-21 8:22 ` [patch 2/2] mm: handle unaligned zones Nick Piggin
2006-05-21 9:19 ` Andrew Morton
2006-05-21 10:31 ` Nick Piggin
2006-05-21 10:59 ` Andrew Morton
2006-05-21 11:44 ` Nick Piggin
2006-05-21 11:52 ` Nick Piggin
2006-05-22 9:24 ` Mel Gorman
2006-05-22 9:28 ` Mel Gorman
2006-05-22 9:06 ` Mel Gorman
2006-05-22 9:51 ` Nick Piggin
2006-05-21 11:53 ` Nick Piggin
2006-05-22 8:18 ` Andy Whitcroft
2006-05-22 9:37 ` Nick Piggin
2006-05-22 9:52 ` [PATCH 0/2] Zone boundary alignment fixes, default configuration Andy Whitcroft
2006-05-22 9:53 ` Andy Whitcroft [this message]
2006-05-22 9:53 ` [PATCH 2/2] x86 add zone alignment qualifier Andy Whitcroft
2006-05-25 11:19 ` [PATCH 0/2] Zone boundary alignment fixes, default configuration Andy Whitcroft
2006-05-31 0:13 ` [stable] " Chris Wright
2006-05-31 11:41 ` Nick Piggin
2006-05-31 12:08 ` Andy Whitcroft
2006-05-31 17:42 ` Greg KH
2006-05-31 17:16 ` Andy Whitcroft
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=20060522095311.GA6869@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nickpiggin@yahoo.com.au \
--cc=stable@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