linux-kernel - Re: [PATCH] splitlru: BDI_CAP_SWAP

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:	Mon, 30 Jun 2008 15:49:12 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lee Schermerhorn <lee.schermerhorn@...com>,
	Nick Piggin <npiggin@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] splitlru: BDI_CAP_SWAP_BACKED

On Mon, 30 Jun 2008 20:23:54 +0100 (BST)
Hugh Dickins <hugh@...itas.com> wrote:

> On Mon, 30 Jun 2008, KAMEZAWA Hiroyuki wrote:
> > 
> > Hmm, how about adding LRU only for shmem/tmpfs ? nonsense ? ;)
> 
> I'd much prefer not: the more LRUs, the more balancing problems;
> And I don't think shmem/tmpfs _deserves_ its own LRUs.
> But it cannot be ruled out.

Tmpfs is often in the same boat as anonymous memory.
Used for shared memory segments, or for files that
are temporary and will be gone soon.

If swap space runs out, tmpfs pages should not be
scanned.

To me, this suggests they should probably continue
to live on the *_ANON LRUs.  Worst case we make
tmpfs pages in files that are not mmaped (/tmp use)
start out on the inactive list, so they get evicted
first.

-- 
All rights reversed.
--
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/