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]
Message-ID: <afe668f90701151834u13c75a88sa4592a4a9482d510@mail.gmail.com>
Date:	Tue, 16 Jan 2007 10:34:52 +0800
From:	"Roy Huang" <royhuang9@...il.com>
To:	balbir@...ibm.com
Cc:	linux-kernel@...r.kernel.org, aubreylee@...il.com,
	nickpiggin@...oo.com.au, torvalds@...l.org
Subject: Re: [PATCH] Provide an interface to limit total page cache.

Hi Balbir,

Thanks for your comment.

On 1/15/07, Balbir Singh <balbir@...ibm.com> wrote:

> wakeup_kswapd and shrink_all_memory use swappiness to determine what to reclaim
> (mapped pages or page cache).  This patch does not ensure that only
> page cache is
> reclaimed/limited. If the swappiness value is high, mapped pages will be hit.
>
You are right, it is possible to release mapped pages. It can be
avoided by add a field in "struct scan_control" to determine whether
mapped pages will be released.

> One could get similar functionality by implementing resource management.
>
> Resource  management splits tasks into groups and does management of
> resources for the
> groups rather than the whole system. Such a facility will come with a
> resource controller for
> memory (split into finer grain rss/page cache/mlock'ed memory, etc),
> one for cpu, etc.
I s there any more information in detail about resource controller?
Even there is a resource controller for tasks, all memory is also
possbile to be eaten up by page cache.
>
> Balbir
>
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ