From: Mike Kravetz <kravetz@us.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/7] ppc64 - Specify amount of kernel memory at boot time
Date: Thu, 23 Feb 2006 09:40:24 -0800 [thread overview]
Message-ID: <20060223174024.GB5699@w-mikek2.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602231646530.24093@skynet.skynet.ie>
On Thu, Feb 23, 2006 at 05:19:19PM +0000, Mel Gorman wrote:
> On Thu, 23 Feb 2006, Dave Hansen wrote:
>
> >On Wed, 2006-02-22 at 16:43 +0000, Mel Gorman wrote:
> >>Is this a bit clearer? It's built and boot tested on one ppc64 machine. I
> >>am having trouble finding a ppc64 machine that *has* memory holes to be
> >>100% sure it's ok.
> >
> >Yeah, it looks that way. If you need a machine, see Mike Kravetz. I
> >think he was working on a way to automate creating memory holes.
> >
>
> Will do. If there is an automatic way of creating holes, I'll write it
> into the current "compare two running kernels" testing script.
I don't realy have an automatic way to create holes. Just turns out that
the system I was working with was good at creating them itself.
I've sliced and diced (made lots of partitioning changes) the system
recently and am still working on getting everything working right.
When I get everything working again, I'll give the patch set a try.
--
Mike
--
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-23 17:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 14:15 [PATCH 0/7] Reducing fragmentation using zones v5 Mel Gorman
2006-02-17 14:16 ` [PATCH 1/7] Add __GFP_EASYRCLM flag and update callers Mel Gorman
2006-02-17 14:16 ` [PATCH 2/7] Create the ZONE_EASYRCLM zone Mel Gorman
2006-02-17 14:16 ` [PATCH 3/7] x86 - Specify amount of kernel memory at boot time Mel Gorman
2006-02-17 14:17 ` [PATCH 4/7] ppc64 " Mel Gorman
2006-02-17 17:16 ` Dave Hansen
2006-02-17 19:03 ` Mel Gorman
2006-02-17 19:17 ` Dave Hansen
2006-02-17 19:36 ` Mel Gorman
2006-02-17 21:31 ` Joel Schopp
2006-02-21 14:51 ` Mel Gorman
2006-02-21 17:35 ` Dave Hansen
2006-02-22 16:43 ` Mel Gorman
2006-02-23 16:42 ` Dave Hansen
2006-02-23 17:19 ` Mel Gorman
2006-02-23 17:38 ` Dave Hansen
2006-02-23 18:01 ` Mel Gorman
2006-02-23 18:15 ` Dave Hansen
2006-02-24 0:15 ` KAMEZAWA Hiroyuki
2006-02-24 9:04 ` Mel Gorman
2006-02-23 17:40 ` Mike Kravetz [this message]
2006-02-17 14:17 ` [PATCH 5/7] At boot, determine what zone memory will hot-add to Mel Gorman
2006-02-17 14:17 ` [PATCH 6/7] Allow HugeTLB allocations to use ZONE_EASYRCLM Mel Gorman
2006-02-17 14:18 ` [PATCH 7/7] Add documentation for extra boot parameters 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=20060223174024.GB5699@w-mikek2.ibm.com \
--to=kravetz@us.ibm.com \
--cc=haveblue@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox