public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv1 0/8] zram: introduce multi-handle entries
Date: Tue, 19 Nov 2024 18:20:59 +0900	[thread overview]
Message-ID: <20241119092059.GC2668855@google.com> (raw)
In-Reply-To: <20241119072057.3440039-1-senozhatsky@chromium.org>

On (24/11/19 16:20), Sergey Senozhatsky wrote:
> 	ZRAM_HUGE objects are incompressible and each takes a whole
> physical page on the zsmalloc side.  zsmalloc pool, naturally, has
> some internal memory fragmentation (within size-classes), so what
> we can do for ZRAM_HUGE objects is to split them into several
> smaller objects (2 at this point) and store those parts individually
> in regular size-classes (hence multi-handle entries). This, basically,
> lets us to use already allocated (but unused) zspages memory for
> ZRAM_HUGE objects, instead of unconditional allocation of 0-order
> page for each ZRAM_HUGE object.

Forgot to mention, this is still just "RFC".

      parent reply	other threads:[~2024-11-19  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19  7:20 [PATCHv1 0/8] zram: introduce multi-handle entries Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 1/8] zram: cond_resched() in writeback loop Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 2/8] zram: free slot memory early during write Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 3/8] zram: remove entry element member Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 4/8] zram: factor out ZRAM_SAME write Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 5/8] zram: factor out ZRAM_HUGE write Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 6/8] zram: factor out ZRAM_HUGE read Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 7/8] zsmalloc: move ZS_HANDLE_SIZE to zsmalloc header Sergey Senozhatsky
2024-11-19  7:20 ` [PATCHv1 8/8] zram: introduce multi-handle entries Sergey Senozhatsky
2024-11-19  9:20 ` Sergey Senozhatsky [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=20241119092059.GC2668855@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@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