From: Michal Hocko <mhocko@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hailong Liu <hailong.liu@oppo.com>,
Barry Song <21cnbao@gmail.com>,
Lokesh Gidra <lokeshgidra@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Nicolas Geoffray <ngeoffray@google.com>, gaoxu <gaoxu2@honor.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shaohua Li <shli@fb.com>, yipengxiang <yipengxiang@honor.com>,
fengbaopeng <fengbaopeng@honor.com>,
Kalesh Singh <kaleshsingh@google.com>
Subject: Re: [PATCH v2] mm: add lazyfree folio to lru tail
Date: Tue, 10 Sep 2024 10:20:47 +0200 [thread overview]
Message-ID: <ZuABX8ohRClBagqp@tiehlicka> (raw)
In-Reply-To: <20240909152215.31e85028c4d09681f09e7509@linux-foundation.org>
On Mon 09-09-24 15:22:15, Andrew Morton wrote:
[...]
> I'm not seeing much clarity on whether we should merge this change. I
> think I'll drop this version - let's please revisit after -rc1.
I think the biggest thing to focus on is the change of the behavior and
whether LIFO aging strategy for MADV_FREE pages is really desirable. It
is a noticeable LRU antipattern.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2024-09-10 8:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:48 [PATCH v2] mm: add lazyfree folio to lru tail gaoxu
2024-08-16 10:19 ` David Hildenbrand
2024-08-16 10:21 ` David Hildenbrand
2024-08-19 16:11 ` Suren Baghdasaryan
2024-08-20 10:11 ` Barry Song
2024-08-20 11:53 ` 回复: " gaoxu
2024-08-20 21:46 ` Barry Song
2024-08-21 12:46 ` Michal Hocko
2024-08-21 21:47 ` Barry Song
2024-08-23 23:39 ` Suren Baghdasaryan
2024-08-26 16:37 ` Lokesh Gidra
2024-08-26 19:54 ` Barry Song
2024-08-27 0:12 ` Lokesh Gidra
2024-08-27 2:21 ` Barry Song
2024-08-27 4:07 ` 回复: " gaoxu
2024-08-27 17:56 ` Minchan Kim
2024-08-29 3:55 ` 回复: " gaoxu
2024-09-10 8:51 ` Barry Song
2024-08-27 2:13 ` Hailong Liu
2024-08-27 2:18 ` Barry Song
2024-08-27 2:29 ` Hailong Liu
2024-09-09 22:22 ` Andrew Morton
2024-09-10 8:20 ` Michal Hocko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZuABX8ohRClBagqp@tiehlicka \
--to=mhocko@suse.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fengbaopeng@honor.com \
--cc=gaoxu2@honor.com \
--cc=hailong.liu@oppo.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=ngeoffray@google.com \
--cc=shli@fb.com \
--cc=surenb@google.com \
--cc=yipengxiang@honor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).