linux-kernel - Re: Fwd: Control page reclaim granularity

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: <CAFPAmTTO6FhwfW1ObbHUpv0qi1a-1321Mwkm+jZVaOvbLaGmxw@mail.gmail.com>
Date:	Tue, 13 Mar 2012 14:33:47 +0530
From:	Kautuk Consul <consul.kautuk@...il.com>
To:	minchan@...nel.org, riel@...hat.com,
	kosaki.motohiro@...fujitsu.com, Zheng Liu <wenqing.lz@...bao.com>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: Fwd: Control page reclaim granularity

> The only problem that might happen might be in OOM because we will
> have to include selection points for
> these page-cache pages (proportionately) while finding the most
> expensive process to kill.
> ( I'm talking about the page-cache pages which are not mapped to
> usermode page-tables at all. )
>
> If any usermode application reads in an extremely huge file, whose
> inode has been set to AS_UNEVICTABLE,
> we might want to kill those applications that read in those
> pages(proportionately) so that the guilty application
> can be killed.

On some more thought, I guess for OOM and proprtionate working set accounting,
the approach mentioned by Konstantin (with fake VMA) should work fine
with respect to the
way oom_kill.c accounts for virtual address size of kill candidates.

So, I now think that the best way might indeed be to have a fake VMA
to account for the
page-cache pages not mapped to usermode.
--
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/