From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH RFC 4/7] zram: Introduce recompress sysfs knob
Date: Mon, 12 Sep 2022 19:05:33 +0900 [thread overview]
Message-ID: <Yx8EbYy2QP1BgS6O@google.com> (raw)
In-Reply-To: <20220905082323.2742399-5-senozhatsky@chromium.org>
On (22/09/05 17:23), Sergey Senozhatsky wrote:
[..]
> + /*
> + * Either a compression error or we failed to compressed the object
> + * in a way that will save us memory. Mark object as "recompressed"
> + * if it's huge, so that we don't try to recompress it again. Ideally
> + * we want to set some bit for all such objects, but we for now do so
> + * only for huge ones (we are out of bits in flags on 32-bit systems).
> + */
This limitation goes away once we move ZRAM_FLAG_SHIFT to
more reasonable value. I can introduce one more pageflag
that will be set for objects that cannot be compressed by
either compression algorithm.
next prev parent reply other threads:[~2022-09-12 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 8:23 [PATCH RFC 0/7] zram: Support multiple compression streams Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 1/7] zram: Preparation for multi-zcomp support Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 2/7] zram: Add recompression algorithm sysfs knob Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 3/7] zram: Factor out WB and non-WB zram read functions Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 4/7] zram: Introduce recompress sysfs knob Sergey Senozhatsky
2022-09-12 10:05 ` Sergey Senozhatsky [this message]
2022-09-05 8:23 ` [PATCH RFC 5/7] documentation: Add recompression documentation Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 6/7] zram: Add recompression algorithm choice to Kconfig Sergey Senozhatsky
2022-09-05 8:23 ` [PATCH RFC 7/7] zram: Add recompress flag to read_block_state() Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 8:15 [PATCH RFC 0/7] zram: Support multiple compression streams Sergey Senozhatsky
2022-09-05 8:15 ` [PATCH RFC 4/7] zram: Introduce recompress sysfs knob Sergey Senozhatsky
2022-09-05 9:21 ` Barry Song
2022-09-05 9:53 ` Sergey Senozhatsky
2022-09-05 10:06 ` Barry Song
2022-09-05 10:17 ` Sergey Senozhatsky
2022-09-05 21:27 ` Barry Song
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=Yx8EbYy2QP1BgS6O@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.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.