Re: [Lhms-devel] Re: [PATCH 0/9] Reducing fragmentation using zones v4

[Mel Gorman <mel@csn.ul.ie>]

On Fri, 27 Jan 2006, KAMEZAWA Hiroyuki wrote:

> 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 :(

Not a problem. If nothing else, testing CONFIG_HIGHMEM showed that there
is a compile bug when memory hotplug is set but highmem is not, so some
good came of this. At least I know you are trying the patches out :)

> This was problem of my tree...
>
> Sigh, I should be more carefull.
> my note is attached.
>
> Sorry,

Not to worry, thanks for the note.

> -- 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....
>
>

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/