From: Chris Li <chrisl@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chengming Zhou <chengming.zhou@linux.dev>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Nhat Pham <nphamcs@gmail.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Takero Funaki <flintglass@gmail.com>
Subject: Re: [PATCH v2] mm/zswap: store <PAGE_SIZE compression failed page as-is
Date: Fri, 15 Aug 2025 15:38:06 -0700 [thread overview]
Message-ID: <CAF8kJuNEeQ14p-VpgRvTJ0YiXLHbc4Y8wSrOOMsnug8oP_bOHg@mail.gmail.com> (raw)
In-Reply-To: <2f75a76c-bdc1-6ca7-4438-21554831ec56@google.com>
On Wed, Aug 13, 2025 at 11:58 AM Hugh Dickins <hughd@google.com> wrote:
>
> On Wed, 13 Aug 2025, Chris Li wrote:
> >
> > I know Hugh has some idea to store incompressible pages in the swap
> > cache as well. Hugh?
>
> No, I don't have any idea or plan to store incompressible pages in the
> swap cache myself. But yes, incompressible pages could well be "stored"
> in the swap cache.
Sorry Hugh, I don't mean to assign you more work. Just brainstorming.
Yes it could. The pros will be no swap fault. The cons is breaking the
zswap LRU ordering.
Chris
next prev parent reply other threads:[~2025-08-15 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 17:00 SeongJae Park
2025-08-12 18:52 ` Nhat Pham
2025-08-13 17:07 ` Chris Li
2025-08-13 18:20 ` SeongJae Park
2025-08-15 22:28 ` Chris Li
2025-08-15 23:08 ` Nhat Pham
2025-08-16 0:14 ` SeongJae Park
2025-08-16 2:23 ` Chris Li
2025-08-18 18:18 ` SeongJae Park
2025-08-18 20:33 ` Chris Li
2025-08-16 0:30 ` Chris Li
2025-08-16 0:07 ` SeongJae Park
2025-08-16 2:20 ` Chris Li
2025-08-13 18:32 ` Nhat Pham
2025-08-15 22:34 ` Chris Li
2025-08-15 22:44 ` Nhat Pham
2025-08-13 18:58 ` Hugh Dickins
2025-08-15 22:38 ` Chris Li [this message]
2025-08-13 19:42 ` Shakeel Butt
2025-08-13 20:48 ` Johannes Weiner
2025-08-15 22:44 ` Chris Li
2025-08-15 22:42 ` Chris Li
2025-08-14 16:23 ` Johannes Weiner
2025-08-14 17:04 ` SeongJae Park
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=CAF8kJuNEeQ14p-VpgRvTJ0YiXLHbc4Y8wSrOOMsnug8oP_bOHg@mail.gmail.com \
--to=chrisl@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=flintglass@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=sj@kernel.org \
--cc=yosry.ahmed@linux.dev \
/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