From: Andy Whitcroft <apw@shadowen.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
Mel Gorman <mel@csn.ul.ie>,
stable@kernel.org, Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [stable] [PATCH 0/2] Zone boundary alignment fixes, default configuration
Date: Wed, 31 May 2006 13:08:05 +0100 [thread overview]
Message-ID: <447D8725.4060506@shadowen.org> (raw)
In-Reply-To: <447D80ED.7070403@yahoo.com.au>
Nick Piggin wrote:
> Chris Wright wrote:
>
>> * Andy Whitcroft (apw@shadowen.org) wrote:
>>
>>> I think a concensus is forming that the checks for merging across
>>> zones were removed from the buddy allocator without anyone noticing.
>>> So I propose that the configuration option UNALIGNED_ZONE_BOUNDARIES
>>> default to on, and those architectures which have been auditied
>>> for alignment may turn it off.
>>
>>
>>
>> So what's the final outcome here for -stable? The only
>> relevant patch upstream appears to be Bob Picco's patch
>
>
> I think you need zone checks? [ ie. page_zone(page) == page_zone(buddy) ]
> I had assumed Andy was going to do a patch for that.
The stack for the full optional check in -mm seems like a lot for a
stable patch. I think for stable we should just add the check for
unconditionally, its very light weight and safe that way. Am just
putting together a patch for that now. Will respond to this email
shortly with that patch once its been through a few tests.
-apw
--
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-31 12:08 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 ` [PATCH 1/2] zone allow unaligned zone boundaries add configuration Andy Whitcroft
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 [this message]
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=447D8725.4060506@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.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