Re: [PATCH mmotm] vmscan: handle may_swap more strictly (Re: [PATCH mmotm] vmscan: fix may_swap handling for memcg)
- From: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>
- Date: Tue, 9 Jun 2009 16:58:36 +0900 (JST)
Hi, KOSAKI.
As you know, this problem caused by if condition(priority) in shrink_zone.
Let me have a question.
Why do we have to prevent scan value calculation when the priority is zero ?
As I know, before split-lru, we didn't do it.
Is there any specific issue in case of the priority is zero ?
Yes.
example:
get_scan_ratio() return anon:80%, file=20%. and the system have
10000 anon pages and 10000 file pages.
shrink_zone() picked up 8000 anon pages and 2000 file pages.
it mean 8000 file pages aren't scanned at all.
Oops, it can makes OOM-killer although system have droppable file cache.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Prev by Date: Re: [Bug #13319] Page allocation failures with b43 and p54usb
- Next by Date: Re: [PATCH] perf_counter: extensible perf_counter_attr
- Previous by thread: Re: [PATCH mmotm] vmscan: handle may_swap more strictly (Re: [PATCH mmotm] vmscan: fix may_swap handling for memcg)
- Next by thread: Re: [PATCH mmotm] vmscan: handle may_swap more strictly (Re: [PATCH mmotm] vmscan: fix may_swap handling for memcg)
- Index(es):
Relevant Pages
|
