linux-kernel - Re: [PATCH v2] mm: add lazyfree folio to lru tail

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: <ZsXho27uAbQ5rEgS@tiehlicka>
Date: Wed, 21 Aug 2024 14:46:27 +0200
From: Michal Hocko <mhocko@...e.com>
To: gaoxu <gaoxu2@...or.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Suren Baghdasaryan <surenb@...gle.com>, Shaohua Li <shli@...com>,
	yipengxiang <yipengxiang@...or.com>,
	fengbaopeng <fengbaopeng@...or.com>,
	Kalesh Singh <kaleshsingh@...gle.com>
Subject: Re: [PATCH v2] mm: add lazyfree folio to lru tail

On Fri 16-08-24 07:48:01, gaoxu wrote:
> Replace lruvec_add_folio with lruvec_add_folio_tail in the lru_lazyfree_fn:
> 1. The lazy-free folio is added to the LRU_INACTIVE_FILE list. If it's
>    moved to the LRU tail, it allows for faster release lazy-free folio and
>    reduces the impact on file refault.

This has been discussed when MADV_FREE was introduced. The question was
whether this memory has a lower priority than other inactive memory that
has been marked that way longer ago. Also consider several MADV_FREE
users should they be LIFO from the reclaim POV?

-- 
Michal Hocko
SUSE Labs