From: Mel Gorman <mel@csn.ul.ie>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] [PATCH 4/9] ppc64 - Specify amount of kernel memory at boot time
Date: Wed, 8 Feb 2006 10:23:42 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0602081022090.20544@skynet> (raw)
In-Reply-To: <43E90BC1.7010907@austin.ibm.com>
On Tue, 7 Feb 2006, Joel Schopp wrote:
> > This patch adds the kernelcore= parameter for ppc64
>
> ...
>
> > diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
> > linux-2.6.16-rc1-mm3-103_x86coremem/mm/page_alloc.c
> > linux-2.6.16-rc1-mm3-104_ppc64coremem/mm/page_alloc.c
> > --- linux-2.6.16-rc1-mm3-103_x86coremem/mm/page_alloc.c 2006-01-26
> > 18:09:04.000000000 +0000
> > +++ linux-2.6.16-rc1-mm3-104_ppc64coremem/mm/page_alloc.c 2006-01-26
> > 18:10:29.000000000 +0000
>
> Not to nitpick, but this chunk should go in a different patch, it's not ppc64
> specific.
>
You're right. It was put in here because it was testing this patch on
ppc64 that the bug was revealed. It should be moved to the patch that adds
the actual zone.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2006-02-08 10:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 18:43 [PATCH 0/9] Reducing fragmentation using zones v4 Mel Gorman
2006-01-26 18:43 ` [PATCH 1/9] Add __GFP_EASYRCLM flag and update callers Mel Gorman
2006-01-26 18:43 ` [PATCH 2/9] Create the ZONE_EASYRCLM zone Mel Gorman
2006-01-26 18:44 ` [PATCH 3/9] x86 - Specify amount of kernel memory at boot time Mel Gorman
2006-01-26 18:44 ` [PATCH 4/9] ppc64 " Mel Gorman
2006-02-07 21:06 ` [Lhms-devel] " Joel Schopp
2006-02-08 10:23 ` Mel Gorman [this message]
2006-01-26 18:44 ` [PATCH 5/9] At boot, determine what zone memory will hot-add to Mel Gorman
2006-01-26 18:45 ` [PATCH 6/9] Allow HugeTLB allocations to use ZONE_EASYRCLM Mel Gorman
2006-01-26 18:45 ` [PATCH 7/9] Add documentation for extra boot parameters Mel Gorman
2006-01-26 18:45 ` [PATCH 8/9] ForTesting - Prevent OOM killer firing for high-order allocations Mel Gorman
2006-01-26 18:46 ` [PATCH 9/9] ForTesting - Drain the per-cpu caches with high order allocations fail Mel Gorman
2006-01-27 0:29 ` [PATCH 0/9] Reducing fragmentation using zones v4 KAMEZAWA Hiroyuki
2006-01-27 0:41 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-01-27 10:29 ` Mel Gorman
2006-01-27 11:19 ` KAMEZAWA Hiroyuki
2006-01-27 11:42 ` 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.58.0602081022090.20544@skynet \
--to=mel@csn.ul.ie \
--cc=jschopp@austin.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).