linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitalywool@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Linux-MM <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Dan Streetman <ddstreet@ieee.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	 LKML <linux-kernel@vger.kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	 Shakeel Butt <shakeelb@google.com>,
	Henry Burns <henrywolfeburns@gmail.com>,
	 "Theodore Ts'o" <tytso@thunk.org>
Subject: Re: [PATCHv2 0/3] Allow ZRAM to use any zpool-compatible backend
Date: Fri, 20 Dec 2019 07:04:05 +0100	[thread overview]
Message-ID: <CAMJBoFPrPuPpcfNCKGF0EkSZ+0R7Un6HuoQhBPsznjVTUkVBSQ@mail.gmail.com> (raw)
In-Reply-To: <20191220031357.GA39061@google.com>

On Fri, Dec 20, 2019 at 4:14 AM Minchan Kim <minchan@kernel.org> wrote:

<snip>
> Look https://lkml.org/lkml/2019/10/29/1169
>
> z3fold read is 15% faster *only* when when compression ratio is bad below 50%
> since zsmalloc involves copy operation if the object is located in the
> boundary of discrete pages. It's never popular workload.
> Even, once write is involved(write-only, mixed read-write), z3fold is always
> slow. Think about that swap-in could cause swap out in the field because devices
> are usually under memory pressure. Also, look at the memory usage.
> zsmalloc saves bigger memory for all of compression ratios.

Yes I remember that. Since your measurements were done on "an x86" without
providing any detail on the actual platform used, they are as good as none.

~Vitaly


      reply	other threads:[~2019-12-20  6:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 14:19 [PATCHv2 0/3] Allow ZRAM to use any zpool-compatible backend Vitaly Wool
2019-12-19 14:21 ` [PATCHv2 1/3] zpool: add compaction api Vitaly Wool
2019-12-19 14:26 ` [PATCHv2 2/3] zsmalloc: add compaction and huge class callbacks Vitaly Wool
2019-12-19 14:27 ` [PATCHv2 3/3] zram: use common zpool interface Vitaly Wool
2019-12-20  3:13 ` [PATCHv2 0/3] Allow ZRAM to use any zpool-compatible backend Minchan Kim
2019-12-20  6:04   ` Vitaly Wool [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=CAMJBoFPrPuPpcfNCKGF0EkSZ+0R7Un6HuoQhBPsznjVTUkVBSQ@mail.gmail.com \
    --to=vitalywool@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ddstreet@ieee.org \
    --cc=henrywolfeburns@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=shakeelb@google.com \
    --cc=tytso@thunk.org \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).