From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, terrelln@fb.com
Subject: Re: + zram-move-from-crypto-api-to-custom-comp-backends-api.patch added to mm-unstable branch
Date: Tue, 25 Jun 2024 00:51:32 +0900 [thread overview]
Message-ID: <20240624155132.GC3130923@google.com> (raw)
In-Reply-To: <ZnmRDl_mZOP2XxtO@google.com>
On (24/06/24 08:30), Minchan Kim wrote:
> > > This patch will shortly appear at
> > > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-move-from-crypto-api-to-custom-comp-backends-api.patch
> >
> > Hello Andrew,
> >
> > May I please ask you to drop this entire series? Apologies for
> > inconvenience.
>
> Hey Sergey,
>
> I didn't catch up all yet but why do you want to drop it?
Hello Minchan,
I should have provided more context, sorry.
The reason being is that I want to rework the series. For example,
I don't really like the way I handle zstd C/D dicts and the whole
->init_config/->release_config for per-CPU compression contexts.
We, quite likely, can move compression contexts out of per-CPU area
entirely, and have a single context per alrogithm. It's only workmem
that cannot be shared and hence should stay in per-CPU.
next prev parent reply other threads:[~2024-06-24 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:31 + zram-move-from-crypto-api-to-custom-comp-backends-api.patch added to mm-unstable branch Andrew Morton
2024-06-24 3:33 ` Sergey Senozhatsky
2024-06-24 15:30 ` Minchan Kim
2024-06-24 15:51 ` Sergey Senozhatsky [this message]
2024-06-24 19:46 ` Minchan Kim
2024-06-24 20:07 ` Andrew Morton
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=20240624155132.GC3130923@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=terrelln@fb.com \
/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.