All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@osdl.org>, Mel Gorman <mel@csn.ul.ie>,
	stable@kernel.org, Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch 2/2] mm: handle unaligned zones
Date: Mon, 22 May 2006 19:37:54 +1000	[thread overview]
Message-ID: <44718672.8050408@yahoo.com.au> (raw)
In-Reply-To: <447173EF.9090000@shadowen.org>

Andy Whitcroft wrote:

> Ok.  I agree that that unaligned zones should be opt-in, it always was

Yes.

> However, this patch here seems redundant.  The requirement from the
> buddy allocator has been an aligned node_mem_map out to MAX_ORDER either
> side of the zones in that node.  With the recent patch from Bob Picco it
> is now allocated that way always.  So we will always have a page* from
> either the adjoining zone or from the node_mem_map padding to examine
> when we are looking for a buddy to coelesce with.  It should always be
> safe to examine that page*'s flags to see if its free to coelesce.  For
> pages outside any zone PG_buddy will never be true, for those in another
> zone the page_zone_idx() check is sufficient.

That's true - does this cover all architectures that do not define
CONFIG_HOLES_IN_ZONE ?

> With the page_zone_idx check enabled and the node_mem_map aligned, I
> cannot see why we would also need to check the zone pfn numbers too?  If
> we did need to check them, then there would be no benefit in checking
> the page_zone_idx as that check would always succeed.

Yes. BTW. are the struct pages outside the nodes going to be correctly
aligned? Either way, I think we should also check that everything has
been set up in the way we expect at meminit time (see my debug function).

> 
> I think the smallest, lightest weight set of changes for this problem is
> the node_mem_map alignement patch from Bob Picco, plus the changes to
> add just the page_zone_idx checks to the allocator.  If the stack that

Yes, that sounds fine.

> makes this an opt-out option is too large, a two liner to check just
> page_zone_idx always would be a good option for stable.

I think it is more a question of time for all arch maintainers to verify
rather than size.

If you just mean: you want to negate the meaning of the CONFIG_ option,
and go through and define it in all architectures, I'd be fine with that
too (by opt-in I just mean the check should be turned on until proven
otherwise)

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
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>

  reply	other threads:[~2006-05-22  9:37 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 [this message]
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
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=44718672.8050408@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.