From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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] Re: [PATCH 0/9] Reducing fragmentation using zones v4
Date: Fri, 27 Jan 2006 20:19:57 +0900 [thread overview]
Message-ID: <43DA01DD.9040808@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601271027560.25836@skynet>
Mel Gorman wrote:
> On Fri, 27 Jan 2006, KAMEZAWA Hiroyuki wrote:
>
>> KAMEZAWA Hiroyuki wrote:
>>> Could you add this patch to your set ?
>>> This was needed to boot my x86 machine without HIGHMEM.
>>>
>> Sorry, I sent a wrong patch..
>> This is correct one.
>
> I can add it although I would like to know more about the problem. I tried
> booting with and without CONFIG_HIGHMEM both stock kernels and with
> anti-frag and they all boot fine. What causes your machine to die? Does it
> occur with stock -mm or just with anti-frag?
>
Sorry, it looks there is no problem with your newest set :(
This was problem of my tree...
Sigh, I should be more carefull.
my note is attached.
Sorry,
-- Kame
== Note ==
I replaced si_meminfo() like following
==
#ifdef CONFIG_HIGHMEM
val->totalhigh = nr_total_zonetype_pages(ZONE_HIGHMEM);
val->freehigh = nr_free_zonetype_pages(ZONE_HIGHMEM);
#else
==
If ZONE_HIGHMEM has no pages, val->totalhigh is 0 and mempool for bounce buffer
is not initialized.
But, now
==
#ifdef CONFIG_HIGHMEM
val->totalhigh = totalhigh_pages;
val->freehigh = nr_free_highpages();
#else
==
totalhigh_pages is defined by highstart_pfn and highend_pfn.
By Zone_EasyRclm, totalhigh_pages is not affected.
mempool for bounce buffer is properly initialized....
next prev parent reply other threads:[~2006-01-27 11:20 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
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 [this message]
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=43DA01DD.9040808@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).