All of lore.kernel.org
 help / color / mirror / Atom feed
From: chenqiwu <qiwuchen55@gmail.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	"qiwu.chen" <qiwu.chen@transsion.com>
Subject: Re: [PATCH] zram: add accounting for incompressible pages
Date: Thu, 16 Apr 2026 21:20:16 +0800	[thread overview]
Message-ID: <20260416132016.GA3562@rlk> (raw)
In-Reply-To: <aeCKbSou1_JZw9UK@google.com>

On Thu, Apr 16, 2026 at 04:07:59PM +0900, Sergey Senozhatsky wrote:
> On (26/04/15 18:43), qiwu.chen wrote:
> > 1. Rename write_incompressible_page to write_huge_page since huge page
> > could be recompressed with secondary algorithms.
> 
> Please no. "huge_page" is the most confusing term that zram uses.
>
So what is differece between ZRAM_HUGE and ZRAM_INCOMPRESSIBLE?
In my opinion, the slot is marked as ZRAM_HUGE if primary algorithm
cannot compress the page. the slot is marked as ZRAM_INCOMPRESSIBLE
if scondary algorithms failed to recompress the page in a way that
condary algorithms failed to recompress the page.
The huge page could be recompressed with secondary algorithms with
a certain probability, so it should not be defined as incompressible page.
> > 2. Similar to huge page, add incompressible_pages accounting for current
> > incompressible pages, and incompressible_pages_since accounting for
> > incompressible pages since zram set up. The accounting value can be showed
> > by mm_stat.
> 
> What for?
Add accounting for ZRAM_INCOMPRESSIBLE pages showed by mm_stat, so we can get
how many pages is incompressiable in current system.

      reply	other threads:[~2026-04-16 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 10:43 [PATCH] zram: add accounting for incompressible pages qiwu.chen
2026-04-16  7:07 ` Sergey Senozhatsky
2026-04-16 13:20   ` chenqiwu [this message]

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=20260416132016.GA3562@rlk \
    --to=qiwuchen55@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=qiwu.chen@transsion.com \
    --cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.