> -----Original Message-----
> From: Nhat Pham <nphamcs@gmail.com>
> Sent: Sunday, May 11, 2025 1:53 PM
> To: Sridhar, Kanchana P <kanchana.p.sridhar@intel.com>
> Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> hannes@cmpxchg.org; yosry.ahmed@linux.dev; chengming.zhou@linux.dev;
> usamaarif642@gmail.com; ryan.roberts@arm.com; 21cnbao@gmail.com;
> ying.huang@linux.alibaba.com; akpm@linux-foundation.org; linux-
> crypto@vger.kernel.org; herbert@gondor.apana.org.au;
> davem@davemloft.net; clabbe@baylibre.com; ardb@kernel.org;
> ebiggers@google.com; surenb@google.com; Accardi, Kristen C
> <kristen.c.accardi@intel.com>; Feghali, Wajdi K <wajdi.k.feghali@intel.com>;
> Gopal, Vinodh <vinodh.gopal@intel.com>
> Subject: Re: [PATCH v9 00/19] zswap compression batching
>
> On Wed, Apr 30, 2025 at 4:53 PM Kanchana P Sridhar
> <kanchana.p.sridhar@intel.com> wrote:
> >
> > Changes since v8:
> > =================
> > 1) Rebased to mm-unstable as of 4-21-2025, commit 2c01d9f3c611.
> > 2) Backported commits for reverting request chaining, since these are
> > in cryptodev-2.6 but not yet in mm-unstable: without these backports,
> > deflate-iaa is non-functional in mm-unstable:
> > commit 64929fe8c0a4 ("crypto: acomp - Remove request chaining")
> > commit 5976fe19e240 ("Revert "crypto: testmgr - Add multibuffer acomp
> > testing"")
> > Backported this hotfix as well:
> > commit 002ba346e3d7 ("crypto: scomp - Fix off-by-one bug when
> > calculating last page").
> > 3) crypto_acomp_[de]compress() restored to non-request chained
> > implementations since request chaining has been removed from acomp in
> > commit 64929fe8c0a4 ("crypto: acomp - Remove request chaining").
>
> I'm a bit confused. Which patches on top of mm-unstable do I need from
> the crypto tree as pre-requisite for this patch series? And in which
> order?
Hi Nhat,
As of today's mm-unstable (commit "c68cfbc5048e"), you can apply
patches in this order:
1) commit 64929fe8c0a4 ("crypto: acomp - Remove request chaining")
from the cryptodev-2.6 tree. Or, Patch 0001 in this series that does
the same.
2) Patch 0002 in this series.
3) Skip Patches 0003 and 0004 in this series, since they were not in
mm-unstable when I created this patch series. They are now in
mm-unstable.
4) Apply Patches 0005-0019 in this series.
Thanks,
Kanchana
© 2016 - 2025 Red Hat, Inc.