[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANzGp4LmtbGHO8x1E0E5scgSPCET8d3y5UxGkOrnNry98885kw@mail.gmail.com>
Date: Tue, 30 Jul 2024 10:27:46 +0800
From: Chuanhua Han <chuanhuahan@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Matthew Wilcox <willy@...radead.org>, 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
Christoph Hellwig <hch@...radead.org> 于2024年7月30日周二 00:11写道:
>
> 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.
I disagree, zram is most popular in embedded systems (like Android).
>
>
--
Thanks,
Chuanhua
Powered by blists - more mailing lists