[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DD5DC06.6010204@jp.fujitsu.com>
Date: Fri, 20 May 2011 12:12:06 +0900
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: luto@....edu
CC: minchan.kim@...il.com, kamezawa.hiroyu@...fujitsu.com,
fengguang.wu@...el.com, andi@...stfloor.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, mgorman@...e.de, hannes@...xchg.org,
riel@...hat.com
Subject: Re: Kernel falls apart under light memory pressure (i.e. linking
vmlinux)
> Right after that happened, I hit ctrl-c to kill test_mempressure.sh.
> The system was OK until I typed sync, and then everything hung.
>
> I'm really confused. shrink_inactive_list in
> RECLAIM_MODE_LUMPYRECLAIM will call one of the isolate_pages functions
> with ISOLATE_BOTH. The resulting list goes into shrink_page_list,
> which does VM_BUG_ON(PageActive(page)).
>
> How is that supposed to work?
Usually clear_active_flags() clear PG_active before calling shrink_page_list().
shrink_inactive_list()
isolate_pages_global()
update_isolated_counts()
clear_active_flags()
shrink_page_list()
--
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