From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, ngupta@vflare.org,
minchan@kernel.org, avromanov@sberdevices.ru,
linux-kernel@vger.kernel.org
Subject: Re: + zram-add-size-class-equals-check-into-recompression.patch added to mm-unstable branch
Date: Fri, 28 Oct 2022 11:31:14 +0900 [thread overview]
Message-ID: <Y1s+8ohGRlutI7aI@google.com> (raw)
In-Reply-To: <20221027200348.1BC0FC433C1@smtp.kernel.org>
On (22/10/27 13:03), Andrew Morton wrote:
> The patch titled
> Subject: zram: add size class equals check into recompression
> has been added to the -mm mm-unstable branch. Its filename is
> zram-add-size-class-equals-check-into-recompression.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-add-size-class-equals-check-into-recompression.patch
[..]
> Patch series "zsmalloc/zram: configurable zspage size", v3.
>
> It makes no sense for us to recompress the object if it will be in the
> same size class. We anyway don't get any memory gain. But, at the same
> time, we get a CPU time overhead when inserting this object into zspage
> and decompressing it afterwards.
>
> Link: https://lkml.kernel.org/r/20221027042651.234524-1-senozhatsky@chromium.org
> Link: https://lkml.kernel.org/r/20221027042651.234524-2-senozhatsky@chromium.org
> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Nitin Gupta <ngupta@vflare.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
next prev parent reply other threads:[~2022-10-28 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 20:03 + zram-add-size-class-equals-check-into-recompression.patch added to mm-unstable branch Andrew Morton
2022-10-28 2:31 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-10 0:31 Andrew Morton
2022-10-31 22:28 Andrew Morton
2022-10-24 21:00 Andrew Morton
2022-10-25 2:34 ` 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=Y1s+8ohGRlutI7aI@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=avromanov@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.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.