linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@osdl.org>
Cc: davej@codemonkey.org.uk, tony.luck@intel.com, linux-mm@kvack.org,
	ak@suse.de, bob.picco@hp.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7
Date: Wed, 7 Jun 2006 10:42:20 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606071030100.20653@skynet.skynet.ie> (raw)
In-Reply-To: <20060606164311.27d4af98.akpm@osdl.org>

On Tue, 6 Jun 2006, Andrew Morton wrote:

> On Tue,  6 Jun 2006 14:47:10 +0100 (IST)
> Mel Gorman <mel@csn.ul.ie> wrote:
>
>> This is V7 of the patchset to size zones and memory holes in an
>> architecture-independent manner.
>
> I hope this won't deprive me of my 4 kbyte highmem zone.
>

heh, I think I found the thread you are on about, including your 4kb 
zone.

For future reference, the memory present in zones should be the same 
before and after the patches. Spanned pages and holes will be different on 
x86_64 because I don't account the kernel image and memmap as holes. 
Spanned pages may be different on ia64 as I start nodes on the first real 
page frame, not pfn 0 there and end them at the last real pfn. However, 
present pages should be the same before and after the patch :)

> I won't merge these patches for rc6-mm1 - we already have a few problems in
> this area which I don't think anyone understands yet.
>

I can't argue with that logic as it makes sense with the current 
uncertainties. I'll keep it rebased and resubmit later. In the meantime, 
I'll keep an eye out for issues in -mm that I can hit a kick or two.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

  reply	other threads:[~2006-06-07  9:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 13:47 [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Mel Gorman
2006-06-06 13:47 ` [PATCH 1/5] Introduce mechanism for registering active regions of memory Mel Gorman
2006-06-06 13:47 ` [PATCH 2/5] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-06-06 13:48 ` [PATCH 3/5] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-06-06 13:48 ` [PATCH 4/5] Have x86_64 " Mel Gorman
2006-06-06 13:48 ` [PATCH 5/5] Have ia64 " Mel Gorman
2006-06-06 23:43 ` [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Andrew Morton
2006-06-07  9:42   ` Mel Gorman [this message]
2006-06-07  9:45     ` Andi Kleen
2006-06-07 10:11       ` Mel Gorman
2006-06-07 10:16         ` Andi Kleen
2006-06-07 10:54           ` Mel Gorman
2006-06-07 15:20             ` Andi Kleen
2006-06-07 16:25               ` Mel Gorman
2006-06-09 12:57               ` Mel Gorman

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=Pine.LNX.4.64.0606071030100.20653@skynet.skynet.ie \
    --to=mel@csn.ul.ie \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bob.picco@hp.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).