From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [RFC PATCH 1/2] vmscan don't isolate too many pages
Date: Tue, 07 Jul 2009 14:59:29 -0400 [thread overview]
Message-ID: <4A539B11.5020803@redhat.com> (raw)
In-Reply-To: <20090707184034.0C70.A69D9226@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> FAQ
> -------
> Q: Why do you compared zone accumulate pages, not individual zone pages?
> A: If we check individual zone, #-of-reclaimer is restricted by smallest zone.
> it mean decreasing the performance of the system having small dma zone.
That is a clever solution! I was playing around a bit with
doing it on a per-zone basis. Your idea is much nicer.
However, I can see one potential problem with your patch:
+ nr_inactive += zone_page_state(zone, NR_INACTIVE_ANON);
+ nr_inactive += zone_page_state(zone, NR_INACTIVE_FILE);
+ nr_isolated += zone_page_state(zone, NR_ISOLATED_ANON);
+ nr_isolated += zone_page_state(zone, NR_ISOLATED_FILE);
+ }
+
+ return nr_isolated > nr_inactive;
What if we ran out of swap space, or are not scanning the
anon list at all for some reason?
It is possible that there are no inactive_file pages left,
with all file pages already isolated, and your function
still letting reclaimers through.
This means you could still get a spurious OOM.
I guess I should mail out my (ugly) approach, so we can
compare the two :)
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [RFC PATCH 1/2] vmscan don't isolate too many pages
Date: Tue, 07 Jul 2009 14:59:29 -0400 [thread overview]
Message-ID: <4A539B11.5020803@redhat.com> (raw)
In-Reply-To: <20090707184034.0C70.A69D9226@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> FAQ
> -------
> Q: Why do you compared zone accumulate pages, not individual zone pages?
> A: If we check individual zone, #-of-reclaimer is restricted by smallest zone.
> it mean decreasing the performance of the system having small dma zone.
That is a clever solution! I was playing around a bit with
doing it on a per-zone basis. Your idea is much nicer.
However, I can see one potential problem with your patch:
+ nr_inactive += zone_page_state(zone, NR_INACTIVE_ANON);
+ nr_inactive += zone_page_state(zone, NR_INACTIVE_FILE);
+ nr_isolated += zone_page_state(zone, NR_ISOLATED_ANON);
+ nr_isolated += zone_page_state(zone, NR_ISOLATED_FILE);
+ }
+
+ return nr_isolated > nr_inactive;
What if we ran out of swap space, or are not scanning the
anon list at all for some reason?
It is possible that there are no inactive_file pages left,
with all file pages already isolated, and your function
still letting reclaimers through.
This means you could still get a spurious OOM.
I guess I should mail out my (ugly) approach, so we can
compare the two :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-07-07 18:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 9:40 [RFC PATCH 0/2] fix unnecessary accidental OOM problem on concurrent reclaim KOSAKI Motohiro
2009-07-07 9:40 ` KOSAKI Motohiro
2009-07-07 9:47 ` [RFC PATCH 1/2] vmscan don't isolate too many pages KOSAKI Motohiro
2009-07-07 9:47 ` KOSAKI Motohiro
2009-07-07 13:23 ` Wu Fengguang
2009-07-07 13:23 ` Wu Fengguang
2009-07-07 18:59 ` Rik van Riel [this message]
2009-07-07 18:59 ` Rik van Riel
2009-07-08 3:19 ` Wu Fengguang
2009-07-08 3:19 ` Wu Fengguang
2009-07-09 1:51 ` [RFC PATCH 1/2] vmscan don't isolate too many pages in a zone Rik van Riel
2009-07-09 1:51 ` Rik van Riel
2009-07-09 2:47 ` Wu Fengguang
2009-07-09 2:47 ` Wu Fengguang
2009-07-09 3:07 ` Wu Fengguang
2009-07-09 3:07 ` Wu Fengguang
2009-07-09 7:01 ` KOSAKI Motohiro
2009-07-09 7:01 ` KOSAKI Motohiro
2009-07-09 8:42 ` Wu Fengguang
2009-07-09 8:42 ` Wu Fengguang
2009-07-09 11:07 ` Minchan Kim
2009-07-09 11:07 ` Minchan Kim
2009-07-09 6:39 ` KOSAKI Motohiro
2009-07-09 6:39 ` KOSAKI Motohiro
2009-07-07 23:39 ` [RFC PATCH 1/2] vmscan don't isolate too many pages Minchan Kim
2009-07-07 23:39 ` Minchan Kim
2009-07-09 3:12 ` KOSAKI Motohiro
2009-07-09 3:12 ` KOSAKI Motohiro
2009-07-07 9:48 ` [RFC PATCH 2/2] Don't continue reclaim if the system have plenty free memory KOSAKI Motohiro
2009-07-07 9:48 ` KOSAKI Motohiro
2009-07-07 13:20 ` Minchan Kim
2009-07-07 13:20 ` Minchan Kim
2009-07-09 5:08 ` KOSAKI Motohiro
2009-07-09 5:08 ` KOSAKI Motohiro
2009-07-09 10:58 ` Minchan Kim
2009-07-09 10:58 ` Minchan Kim
2009-07-13 0:37 ` KOSAKI Motohiro
2009-07-13 0:37 ` KOSAKI Motohiro
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=4A539B11.5020803@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.