[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0901020254h13d43d2difa340aa1c40a0dbf@mail.gmail.com>
Date: Fri, 2 Jan 2009 19:54:34 +0900
From: "KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To: "MinChan Kim" <minchan.kim@...il.com>
Cc: "Mel Gorman" <mel@....ul.ie>, LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Nick Piggin" <npiggin@...e.de>,
"wassim dagash" <wassim.dagash@...il.com>
Subject: Re: [PATCH] mm: stop kswapd's infinite loop at high order allocation take2
>>> So I want to balance zone's proportional free page.
>>> How about following ?
>>>
>>> if (nr_reclaimed < SWAP_CLUSTER_MAX) {
>>> if (order != 0) {
>>> order -=1;
>>> sc.order -=1;
>>> }
>>> }
>>>
>>> It prevents infinite loop and do best effort to make zone's
>>> proportional free page per order size good.
>>>
>>> It's just my opinion within my knowledge.
>>> If it have a problem, pz, explain me :)
>>
>> Please read Nick's expalin. it explain very kindly :)
>
> Hm. I read Nick's explain.
> I understand his point.
>
> Nick said,
> "A higher kswapd reclaim order shouldn't weaken kswapd
> postcondition for order-0 memory."
>
> My patch don't prevent order-0 memory reclaim. After all, it will do it.
> It also can do best effort to reclaim other order size.
>
> In this case, others order size reclaim is needless ?
Yes, needless.
wakeup_kswapd() function mean
- please make free memory until pages_high
- and, I want to "order argument" conteniously pages.
then, shorter conteniously pages than "order argumet" pages aren't needed
by caller.
Unfortunately, your patch has more bad side effect.
high order shrink_zone() cause lumpy reclaim.
lumpy reclaim cause reclaim neighbor pages although it is active page.
needlessly active page reclaiming decrease system performance.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists