linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] memory-layout-free zones (for review) [2/3]  remvoe zone_start_pfn/spanned_pages
Date: Thu, 23 Feb 2006 10:06:52 -0800	[thread overview]
Message-ID: <1140718012.8697.63.camel@localhost.localdomain> (raw)
In-Reply-To: <20060223175819.3fbb21fe.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, 2006-02-23 at 17:58 +0900, KAMEZAWA Hiroyuki wrote:
> This patch removes zone_start_pfn/zone_spanned_pages from zone struct.
> (and also removes seqlock for zone resizing)
> 
> By this definion of zone will change
> from : a contiguous range of pages to be used in the same manner.
> to   : a group of pages to be used in the same manner.
> 
> zone will become a pure page_allocator. memory layout is managed by
> pgdat.
> 
> This change has benefit for memory-hotplug and maybe other works.
> We can define a zone which is free from memory layout, like ZONE_EASYRCLM,
> ZONE_EMERGENCY(currently maneged by mempool) etc..witout inconsistency.
> 
> for_each_page_in_zone() uses zone's memory layout information, but this
> patch doesn't include fixes for it. It will be fixed by following patch.

Geez, that removes a bunch of code.  _My_ code.  I like it. :)

-- Dave

--
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-02-23 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  8:58 KAMEZAWA Hiroyuki
2006-02-23 18:06 ` Dave Hansen [this message]

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=1140718012.8697.63.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.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