[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZrnHerW7VV0YKZh1@infradead.org>
Date: Mon, 12 Aug 2024 01:27:38 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Chris Li <chrisl@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>, Barry Song <21cnbao@...il.com>,
Matthew Wilcox <willy@...radead.org>, akpm@...ux-foundation.org,
linux-mm@...ck.org, ying.huang@...el.com,
baolin.wang@...ux.alibaba.com, 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 Thu, Aug 01, 2024 at 01:55:51PM -0700, Chris Li wrote:
> Currently Android uses zram and it needs to be the Android team's
> decision to move from zram to something else. I don't see that
> happening any time soon. There are practical limitations.
No one can tell anyone to stop using things. But we can stop adding
new hacks for this, and especially user facing controls.
Powered by blists - more mailing lists