[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zqe_Nab-Df1CN7iW@infradead.org>
Date: Mon, 29 Jul 2024 09:11:33 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Barry Song <21cnbao@...il.com>, akpm@...ux-foundation.org,
linux-mm@...ck.org, ying.huang@...el.com,
baolin.wang@...ux.alibaba.com, chrisl@...nel.org, david@...hat.com,
hannes@...xchg.org, hughd@...gle.com, kaleshsingh@...gle.com,
kasong@...cent.com, linux-kernel@...r.kernel.org, mhocko@...e.com,
minchan@...nel.org, nphamcs@...il.com, ryan.roberts@....com,
senozhatsky@...omium.org, shakeel.butt@...ux.dev,
shy828301@...il.com, surenb@...gle.com, v-songbaohua@...o.com,
xiang@...nel.org, yosryahmed@...gle.com
Subject: Re: [PATCH v5 4/4] mm: Introduce per-thpsize swapin control policy
On Mon, Jul 29, 2024 at 04:52:30AM +0100, Matthew Wilcox wrote:
> I strongly disagree. Use the same sysctl as the other anonymous memory
> allocations.
I agree with Matthew here.
We also really need to stop optimizing for this weird zram case and move
people to zswap instead after fixing the various issues. A special
block device that isn't really a block device and needs various special
hooks isn't the right abstraction for different zwap strategies.
Powered by blists - more mailing lists