From: Rik van Riel <riel@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Gene Heskett <gene.heskett@gmail.com>
Subject: Re: [PATCH] mm: evict streaming IO cache first
Date: Mon, 17 Nov 2008 11:54:07 -0500 [thread overview]
Message-ID: <4921A1AF.1070909@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0811170830320.3468@nehalem.linux-foundation.org>
Linus Torvalds wrote:
> Another thing strikes me: it looks like the logic in "get_scan_ratio()"
> has a tendency to get unbalanced - if we end up deciding that we should
> scan a lot of anonymous pages, the scan numbers for anonymous pages will
> go up, and we get even _more_ eager to scan those. Of course, "rotate"
> events will then make us less likely again, but for streaming loads, you
> wouldn't expect to see those at all.
True for streaming loads - if we scan the file list and find
mostly pages from streaming loads, we will become more eager
to scan the file list.
I do not expect streaming loads to ever hit the anon list in
the same way, because anonymous pages start out referenced and
on the active list, which means an anonymous deactivation will
always be counted as a rotate event.
> There seems to be another bug there wrt the "aging" - we age anon page
> events and file page events independently, which sounds like it would make
> the math totally nonsensical. We do that whole
>
> anon / (anon + file)
That's an outdated comment. Andrew had a patch to update that
comment, but it must have gotten lost somewhere. I'll send you
a patch to update it.
If you look at the actual calculation, you'l see that the
scan percentages are keyed off just swappiness and the
rotated/scanned ratios for each page category.
--
All rights reversed.
--
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:[~2008-11-17 16:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 9:38 KOSAKI Motohiro
2008-11-16 0:58 ` Rik van Riel
2008-11-16 5:00 ` Andrew Morton
2008-11-16 18:15 ` Linus Torvalds
2008-11-16 21:20 ` Rik van Riel
2008-11-16 21:28 ` Hugh Dickins
2008-11-17 4:47 ` Andrew Morton
2008-11-17 6:19 ` Nick Piggin
2008-11-17 6:30 ` KAMEZAWA Hiroyuki
2008-11-17 6:39 ` KOSAKI Motohiro
2008-11-17 6:54 ` KAMEZAWA Hiroyuki
2008-11-17 7:03 ` KOSAKI Motohiro
2008-11-17 8:22 ` KAMEZAWA Hiroyuki
2008-11-17 8:32 ` KOSAKI Motohiro
2008-11-17 16:22 ` Rik van Riel
2008-11-17 16:22 ` Linus Torvalds
2008-11-17 16:27 ` Rik van Riel
2008-11-17 16:37 ` Linus Torvalds
2008-11-17 16:54 ` Rik van Riel [this message]
2008-11-17 17:06 ` Linus Torvalds
2008-11-17 17:16 ` [PATCH] vmscan: fix get_scan_ratio comment Rik van Riel
2008-11-17 17:32 ` KOSAKI Motohiro
2008-11-17 17:35 ` Linus Torvalds
2008-11-17 18:53 ` Rik van Riel
2008-11-17 20:23 ` Rik van Riel
2008-11-18 0:06 ` [PATCH] vmscan: evict streaming IO first Rik van Riel
2008-12-01 20:24 ` Andrew Morton
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=4921A1AF.1070909@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gene.heskett@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox