linux-kernel - Re: [RFC][PATCH] split file and anonymous page queues #3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Mar 2007 08:01:19 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Nikita Danilov <nikita@...sterfs.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>
Subject: Re: [RFC][PATCH] split file and anonymous page queues #3

Nikita Danilov wrote:

> Probably I am missing something, but I don't see how that can help. For
> example, suppose (for simplicity) that we have swappiness of 100%, and
> that fraction of referenced anon pages gets slightly less than of file
> pages. get_scan_ratio() increases anon_percent, and shrink_zone() starts
> scanning anon queue more aggressively. As a result, pages spend less
> time there, and have less chance of ever being accessed, reducing
> fraction of referenced anon pages further, and triggering further
> increase in the amount of scanning, etc. Doesn't this introduce positive
> feed-back loop?

It's a possibility, but I don't think it will be much of an
issue in practice.

If it is, we can always use refaults as a correcting
mechanism - which would have the added benefit of being
able to do streaming IO without putting any pressure on
the active list, essentially clock-pro replacement with
just some tweaks to shrink_list()...

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.
-
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/