From: Joel Schopp <jschopp@austin.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
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: Tue, 07 Feb 2006 15:06:09 -0600 [thread overview]
Message-ID: <43E90BC1.7010907@austin.ibm.com> (raw)
In-Reply-To: <20060126184425.8550.64598.sendpatchset@skynet.csn.ul.ie>
> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Joel Schopp <jschopp@austin.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
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: Tue, 07 Feb 2006 15:06:09 -0600 [thread overview]
Message-ID: <43E90BC1.7010907@austin.ibm.com> (raw)
In-Reply-To: <20060126184425.8550.64598.sendpatchset@skynet.csn.ul.ie>
> 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.
--
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>
next prev parent reply other threads:[~2006-02-07 21:06 UTC|newest]
Thread overview: 34+ 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 ` Mel Gorman
2006-01-26 18:43 ` [PATCH 1/9] Add __GFP_EASYRCLM flag and update callers Mel Gorman
2006-01-26 18:43 ` Mel Gorman
2006-01-26 18:43 ` [PATCH 2/9] Create the ZONE_EASYRCLM zone Mel Gorman
2006-01-26 18:43 ` 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 ` Mel Gorman
2006-01-26 18:44 ` [PATCH 4/9] ppc64 " Mel Gorman
2006-01-26 18:44 ` Mel Gorman
2006-02-07 21:06 ` Joel Schopp [this message]
2006-02-07 21:06 ` [Lhms-devel] " Joel Schopp
2006-02-08 10:23 ` Mel Gorman
2006-02-08 10:23 ` Mel Gorman
2006-01-26 18:44 ` [PATCH 5/9] At boot, determine what zone memory will hot-add to Mel Gorman
2006-01-26 18:44 ` Mel Gorman
2006-01-26 18:45 ` [PATCH 6/9] Allow HugeTLB allocations to use ZONE_EASYRCLM Mel Gorman
2006-01-26 18:45 ` Mel Gorman
2006-01-26 18:45 ` [PATCH 7/9] Add documentation for extra boot parameters Mel Gorman
2006-01-26 18:45 ` 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:45 ` 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-26 18:46 ` Mel Gorman
2006-01-27 0:29 ` [PATCH 0/9] Reducing fragmentation using zones v4 KAMEZAWA Hiroyuki
2006-01-27 0:29 ` KAMEZAWA Hiroyuki
2006-01-27 0:41 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-01-27 0:41 ` KAMEZAWA Hiroyuki
2006-01-27 10:29 ` Mel Gorman
2006-01-27 10:29 ` Mel Gorman
2006-01-27 11:19 ` KAMEZAWA Hiroyuki
2006-01-27 11:19 ` KAMEZAWA Hiroyuki
2006-01-27 11:42 ` Mel Gorman
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=43E90BC1.7010907@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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.