The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: mel@skynet.ie (Mel Gorman)
Cc: Andrew Morton <akpm@linux-foundation.org>,
	tony.luck@intel.com,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]Fix parsing kernelcore boot option for ia64
Date: Tue, 24 Apr 2007 18:58:57 +0900	[thread overview]
Message-ID: <20070424183847.FD98.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20070423183637.GA11982@skynet.ie>



> Subject: Check zone boundaries when freeing bootmem
> Zone boundaries do not have to be aligned to MAX_ORDER_NR_PAGES. 

Hmm. I don't understand here yet... Could you explain more? 

This issue occurs only when ZONE_MOVABLE is specified.
If its boundary is aligned to MAX_ORDER automatically,
I guess user will not mind it.

>From memory hotplug view, I prefer section size alignment to make
simple code. :-P


> However,
> during boot, there is an implicit assumption that they are aligned to a
> BITS_PER_LONG boundary when freeing pages as quickly as possible. This
> patch checks the zone boundaries when freeing pages from the bootmem allocator.

Anyway, the patch works well.

Bye.

-- 
Yasunori Goto 



  reply	other threads:[~2007-04-24  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  5:26 [PATCH]Fix parsing kernelcore boot option for ia64 Yasunori Goto
2007-04-16 13:29 ` Mel Gorman
2007-04-22  6:22 ` Andrew Morton
2007-04-23 11:46   ` Yasunori Goto
2007-04-23 13:06     ` Mel Gorman
2007-04-23 18:32     ` Mel Gorman
2007-04-23 18:36       ` Mel Gorman
2007-04-24  9:58         ` Yasunori Goto [this message]
2007-04-24 10:09           ` Mel Gorman
2007-04-24 11:50           ` Mel Gorman
2007-04-24  0:26       ` KAMEZAWA Hiroyuki
2007-04-24  7:31         ` Yasunori Goto
2007-04-24 11:55           ` 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=20070424183847.FD98.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@skynet.ie \
    --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