All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	lhms <lhms-devel@lists.sourceforge.net>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [Lhms-devel] [RFC] consistency of zone->zone_start_pfn, spanned_pages
Date: Tue, 17 May 2005 13:32:51 +0100	[thread overview]
Message-ID: <4289E473.1090404@shadowen.org> (raw)
In-Reply-To: <42893D7C.6070907@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:

> How about removing zone_start_pfn and spanned_pages ?
> 
> I found they are used in
>    bad_range() in page_alloc.c
>    mark_free_page() in CONFIG_PM.
> 
> And I think we can remove them with section-range-ops when
> CONFIG_SPARSEMEM=y.
> They are used in some another places ?

This needs careful thought as we use bad_range in __free_pages_bulk() in
a non-debug form to work out whether a free'd page is a member of a zone
when trying to pair it with its buddy.  Take for instance ZONE_DMA on
typical x86 hardware which has 0 complete MAX_ORDER buddies within.

-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:"aart@kvack.org"> aart@kvack.org </a>

      parent reply	other threads:[~2005-05-17 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 16:00 [RFC] consistency of zone->zone_start_pfn, spanned_pages Dave Hansen
2005-05-13 18:24 ` Robin Holt
2005-05-13 18:31   ` Dave Hansen
2005-05-17  9:50   ` Andy Whitcroft
2005-05-17 10:46     ` Robin Holt
2005-05-17  0:40 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2005-05-17  5:43   ` Yasunori Goto
2005-05-17 12:32   ` Andy Whitcroft [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=4289E473.1090404@shadowen.org \
    --to=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --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 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.