Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Chris Wiseman <chriswiseman@google.com>
Cc: Yosry Ahmed <yosry@kernel.org>, Nhat Pham <nphamcs@gmail.com>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	 Xueyuan Chen <xueyuan.chen21@gmail.com>,
	Xueyuan Chen <xueyuan.chen@vivo.com>,
	 Barry Song <baohua@kernel.org>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	 Brian Geffon <bgeffon@google.com>,
	Minchan Kim <minchan@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] mm: zsmalloc: make shrinker compaction budget-aware
Date: Wed, 18 Nov 2026 11:25:15 +0900	[thread overview]
Message-ID: <av0L2-OtxcWpQ09m@google.com> (raw)
In-Reply-To: <18e8fc17375582a2.3137322e32332e3235332e313736.2a6db6.0000sendgmr@google.com>

On (26/11/18 00:27), Chris Wiseman wrote:
> Nhat / Johannes / Sergey - good with a 2-patch series that just removes
> the zsmalloc shrinker and adds the unlocked zs_can_compact() pre-check
> for manual zram compaction?

If there is no shrinker now then does unlocked zs_can_compact() matter
that much?  I assume zs_can_compact() is now called only from external
code, so it's not expected to be executed nearly as often as before, or
is there some other reason to make it unlocked?


  parent reply	other threads:[~2026-11-18  2:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  8:27 [RFC PATCH 0/2] mm: zsmalloc: make shrinker compaction budget-aware xueyuan.chen
2026-08-06  8:27 ` [RFC PATCH 1/2] mm: zsmalloc: add a page limit to pool compaction xueyuan.chen
2026-08-06  8:27 ` [RFC PATCH 2/2] mm: zsmalloc: use the shrinker reclaim budget xueyuan.chen
2026-08-07  3:56 ` [RFC PATCH 0/2] mm: zsmalloc: make shrinker compaction budget-aware Sergey Senozhatsky
2026-08-07 10:57   ` Xueyuan Chen
2026-08-07 12:12     ` Sergey Senozhatsky
2026-08-07 16:25       ` Nhat Pham
2026-08-11  9:03         ` Xueyuan Chen
2026-08-11 16:25           ` Nhat Pham
2026-08-14 16:50             ` Xueyuan Chen
2026-08-18 12:11             ` Xueyuan Chen
2026-10-29  1:43         ` Sergey Senozhatsky
2026-10-29  1:48           ` Sergey Senozhatsky
2026-11-02  2:58             ` Xueyuan Chen
2026-11-04 18:06             ` Nhat Pham
2026-10-30  2:05           ` Xueyuan Chen
2026-10-29  2:26         ` Sergey Senozhatsky
2026-11-01 23:47           ` Sergey Senozhatsky
2026-11-02 20:24             ` Chris Wiseman
2026-11-04 17:57               ` Nhat Pham
2026-11-04 18:46                 ` Chris Wiseman
2026-11-04 21:54                   ` Nhat Pham
2026-11-05  1:10                     ` Xueyuan Chen
2026-11-05  5:05                       ` Sergey Senozhatsky
2026-11-05 13:36                         ` Chris Wiseman
2026-11-05 15:08                           ` Nhat Pham
2026-11-05 15:32                             ` Xueyuan Chen
2026-11-05 15:38                             ` Yosry Ahmed
2026-11-05 15:39                               ` Yosry Ahmed
2026-11-05 16:53                                 ` Chris Wiseman
2026-11-05 16:56                                   ` Yosry Ahmed
2026-11-12  5:58                                   ` Sergey Senozhatsky
2026-11-18  0:13                                     ` Chris Wiseman
2026-11-18  0:23                                       ` Yosry Ahmed
2026-11-18  0:27                                         ` Chris Wiseman
2026-11-18  1:01                                           ` Xueyuan Chen
2026-11-18  2:25                                           ` Sergey Senozhatsky [this message]
2026-11-05 15:24                         ` Xueyuan Chen
2026-11-05  5:01                     ` Sergey Senozhatsky

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=av0L2-OtxcWpQ09m@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=bgeffon@google.com \
    --cc=chriswiseman@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=nphamcs@gmail.com \
    --cc=xueyuan.chen21@gmail.com \
    --cc=xueyuan.chen@vivo.com \
    --cc=yosry.ahmed@linux.dev \
    --cc=yosry@kernel.org \
    /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