linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nhat Pham <nphamcs@gmail.com>
To: Kanchana P Sridhar <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,
	senozhatsky@chromium.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, kristen.c.accardi@intel.com,
	 vinicius.gomes@intel.com, wajdi.k.feghali@intel.com,
	vinodh.gopal@intel.com
Subject: Re: [PATCH v10 20/25] mm: zswap: Move the CPU hotplug procedures under "pool functions".
Date: Fri, 4 Jul 2025 11:39:28 -0700	[thread overview]
Message-ID: <CAKEwX=PFJzc0pErjMcfeeheGL8u4GWMu2yr-iqWmFvYMKfT3fg@mail.gmail.com> (raw)
In-Reply-To: <20250704042323.10318-21-kanchana.p.sridhar@intel.com>

On Thu, Jul 3, 2025 at 9:23 PM Kanchana P Sridhar
<kanchana.p.sridhar@intel.com> wrote:
>
> This patch merely moves zswap_cpu_comp_prepare() and
> zswap_cpu_comp_dead() to be in the "pool functions" section because
> these functions are invoked upon pool creation/deletion.

Hmm idk, "compressed storage" section seems fitting for
zswap_cpu_comp_prepare() and zswap_cpu_comp_dead().

Is this patch necessary?

>
> Signed-off-by: Kanchana P Sridhar <kanchana.p.sridhar@intel.com>
> ---
>  mm/zswap.c | 188 ++++++++++++++++++++++++++---------------------------
>  1 file changed, 94 insertions(+), 94 deletions(-)
>
> diff --git a/mm/zswap.c b/mm/zswap.c
> index 3c0fd8a137182..3538ecaed5e16 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -248,6 +248,100 @@ static inline struct xarray *swap_zswap_tree(swp_entry_t swp)
>  **********************************/
>  static void __zswap_pool_empty(struct percpu_ref *ref);
>
> +static int zswap_cpu_comp_prepare(unsigned int cpu, struct hlist_node *node)
> +{
> +       struct zswap_pool *pool = hlist_entry(node, struct zswap_pool, node);
> +       struct crypto_acomp_ctx *acomp_ctx = per_cpu_ptr(pool->acomp_ctx, cpu);
> +       struct crypto_acomp *acomp = NULL;
> +       struct acomp_req *req = NULL;
> +       u8 *buffer = NULL;
> +       int ret;
> +
> +       buffer = kmalloc_node(PAGE_SIZE * 2, GFP_KERNEL, cpu_to_node(cpu));
> +       if (!buffer) {
> +               ret = -ENOMEM;
> +               goto fail;
> +       }
> +
> +       acomp = crypto_alloc_acomp_node(pool->tfm_name, 0, 0, cpu_to_node(cpu));
> +       if (IS_ERR(acomp)) {
> +               pr_err("could not alloc crypto acomp %s : %ld\n",
> +                               pool->tfm_name, PTR_ERR(acomp));
> +               ret = PTR_ERR(acomp);
> +               goto fail;
> +       }
> +
> +       req = acomp_request_alloc(acomp);
> +       if (!req) {
> +               pr_err("could not alloc crypto acomp_request %s\n",
> +                      pool->tfm_name);
> +               ret = -ENOMEM;
> +               goto fail;
> +       }
> +
> +       /*
> +        * Only hold the mutex after completing allocations, otherwise we may
> +        * recurse into zswap through reclaim and attempt to hold the mutex
> +        * again resulting in a deadlock.
> +        */
> +       mutex_lock(&acomp_ctx->mutex);
> +       crypto_init_wait(&acomp_ctx->wait);
> +
> +       /*
> +        * if the backend of acomp is async zip, crypto_req_done() will wakeup
> +        * crypto_wait_req(); if the backend of acomp is scomp, the callback
> +        * won't be called, crypto_wait_req() will return without blocking.
> +        */
> +       acomp_request_set_callback(req, CRYPTO_TFM_REQ_MAY_BACKLOG,
> +                                  crypto_req_done, &acomp_ctx->wait);
> +
> +       acomp_ctx->buffer = buffer;
> +       acomp_ctx->acomp = acomp;
> +       acomp_ctx->is_sleepable = acomp_is_async(acomp);
> +       acomp_ctx->req = req;
> +       mutex_unlock(&acomp_ctx->mutex);
> +       return 0;
> +
> +fail:
> +       if (acomp)
> +               crypto_free_acomp(acomp);
> +       kfree(buffer);
> +       return ret;
> +}
> +
> +static int zswap_cpu_comp_dead(unsigned int cpu, struct hlist_node *node)
> +{
> +       struct zswap_pool *pool = hlist_entry(node, struct zswap_pool, node);
> +       struct crypto_acomp_ctx *acomp_ctx = per_cpu_ptr(pool->acomp_ctx, cpu);
> +       struct acomp_req *req;
> +       struct crypto_acomp *acomp;
> +       u8 *buffer;
> +
> +       if (IS_ERR_OR_NULL(acomp_ctx))
> +               return 0;
> +
> +       mutex_lock(&acomp_ctx->mutex);
> +       req = acomp_ctx->req;
> +       acomp = acomp_ctx->acomp;
> +       buffer = acomp_ctx->buffer;
> +       acomp_ctx->req = NULL;
> +       acomp_ctx->acomp = NULL;
> +       acomp_ctx->buffer = NULL;
> +       mutex_unlock(&acomp_ctx->mutex);
> +
> +       /*
> +        * Do the actual freeing after releasing the mutex to avoid subtle
> +        * locking dependencies causing deadlocks.
> +        */
> +       if (!IS_ERR_OR_NULL(req))
> +               acomp_request_free(req);
> +       if (!IS_ERR_OR_NULL(acomp))
> +               crypto_free_acomp(acomp);
> +       kfree(buffer);
> +
> +       return 0;
> +}
> +
>  static struct zswap_pool *zswap_pool_create(char *type, char *compressor)
>  {
>         struct zswap_pool *pool;
> @@ -818,100 +912,6 @@ static void zswap_entry_free(struct zswap_entry *entry)
>  /*********************************
>  * compressed storage functions
>  **********************************/
> -static int zswap_cpu_comp_prepare(unsigned int cpu, struct hlist_node *node)
> -{
> -       struct zswap_pool *pool = hlist_entry(node, struct zswap_pool, node);
> -       struct crypto_acomp_ctx *acomp_ctx = per_cpu_ptr(pool->acomp_ctx, cpu);
> -       struct crypto_acomp *acomp = NULL;
> -       struct acomp_req *req = NULL;
> -       u8 *buffer = NULL;
> -       int ret;
> -
> -       buffer = kmalloc_node(PAGE_SIZE * 2, GFP_KERNEL, cpu_to_node(cpu));
> -       if (!buffer) {
> -               ret = -ENOMEM;
> -               goto fail;
> -       }
> -
> -       acomp = crypto_alloc_acomp_node(pool->tfm_name, 0, 0, cpu_to_node(cpu));
> -       if (IS_ERR(acomp)) {
> -               pr_err("could not alloc crypto acomp %s : %ld\n",
> -                               pool->tfm_name, PTR_ERR(acomp));
> -               ret = PTR_ERR(acomp);
> -               goto fail;
> -       }
> -
> -       req = acomp_request_alloc(acomp);
> -       if (!req) {
> -               pr_err("could not alloc crypto acomp_request %s\n",
> -                      pool->tfm_name);
> -               ret = -ENOMEM;
> -               goto fail;
> -       }
> -
> -       /*
> -        * Only hold the mutex after completing allocations, otherwise we may
> -        * recurse into zswap through reclaim and attempt to hold the mutex
> -        * again resulting in a deadlock.
> -        */
> -       mutex_lock(&acomp_ctx->mutex);
> -       crypto_init_wait(&acomp_ctx->wait);
> -
> -       /*
> -        * if the backend of acomp is async zip, crypto_req_done() will wakeup
> -        * crypto_wait_req(); if the backend of acomp is scomp, the callback
> -        * won't be called, crypto_wait_req() will return without blocking.
> -        */
> -       acomp_request_set_callback(req, CRYPTO_TFM_REQ_MAY_BACKLOG,
> -                                  crypto_req_done, &acomp_ctx->wait);
> -
> -       acomp_ctx->buffer = buffer;
> -       acomp_ctx->acomp = acomp;
> -       acomp_ctx->is_sleepable = acomp_is_async(acomp);
> -       acomp_ctx->req = req;
> -       mutex_unlock(&acomp_ctx->mutex);
> -       return 0;
> -
> -fail:
> -       if (acomp)
> -               crypto_free_acomp(acomp);
> -       kfree(buffer);
> -       return ret;
> -}
> -
> -static int zswap_cpu_comp_dead(unsigned int cpu, struct hlist_node *node)
> -{
> -       struct zswap_pool *pool = hlist_entry(node, struct zswap_pool, node);
> -       struct crypto_acomp_ctx *acomp_ctx = per_cpu_ptr(pool->acomp_ctx, cpu);
> -       struct acomp_req *req;
> -       struct crypto_acomp *acomp;
> -       u8 *buffer;
> -
> -       if (IS_ERR_OR_NULL(acomp_ctx))
> -               return 0;
> -
> -       mutex_lock(&acomp_ctx->mutex);
> -       req = acomp_ctx->req;
> -       acomp = acomp_ctx->acomp;
> -       buffer = acomp_ctx->buffer;
> -       acomp_ctx->req = NULL;
> -       acomp_ctx->acomp = NULL;
> -       acomp_ctx->buffer = NULL;
> -       mutex_unlock(&acomp_ctx->mutex);
> -
> -       /*
> -        * Do the actual freeing after releasing the mutex to avoid subtle
> -        * locking dependencies causing deadlocks.
> -        */
> -       if (!IS_ERR_OR_NULL(req))
> -               acomp_request_free(req);
> -       if (!IS_ERR_OR_NULL(acomp))
> -               crypto_free_acomp(acomp);
> -       kfree(buffer);
> -
> -       return 0;
> -}
> -
>  static struct crypto_acomp_ctx *acomp_ctx_get_cpu_lock(struct zswap_pool *pool)
>  {
>         struct crypto_acomp_ctx *acomp_ctx;
> --
> 2.27.0
>


  reply	other threads:[~2025-07-04 18:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04  4:22 [PATCH v10 00/25] zswap compression batching with optimized iaa_crypto driver Kanchana P Sridhar
2025-07-04  4:22 ` [PATCH v10 01/25] crypto: iaa - Reorganize the iaa_crypto driver code Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 02/25] crypto: iaa - New architecture for IAA device WQ comp/decomp usage & core mapping Kanchana P Sridhar
2025-07-05  6:00   ` kernel test robot
2025-07-04  4:23 ` [PATCH v10 03/25] crypto: iaa - Simplify, consistency of function parameters, minor stats bug fix Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 04/25] crypto: iaa - Descriptor allocation timeouts with mitigations Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 05/25] crypto: iaa - iaa_wq uses percpu_refs for get/put reference counting Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 06/25] crypto: iaa - Simplify the code flow in iaa_compress() and iaa_decompress() Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 07/25] crypto: iaa - Refactor hardware descriptor setup into separate procedures Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 08/25] crypto: iaa - Simplified, efficient job submissions for non-irq mode Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 09/25] crypto: iaa - Deprecate exporting add/remove IAA compression modes Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 10/25] crypto: iaa - Rearchitect the iaa_crypto driver to be usable by zswap and zram Kanchana P Sridhar
2025-07-04 15:56   ` kernel test robot
2025-07-05 14:49   ` kernel test robot
2025-07-04  4:23 ` [PATCH v10 11/25] crypto: iaa - Enablers for submitting descriptors then polling for completion Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 12/25] crypto: acomp - Add "void *kernel_data" in "struct acomp_req" for kernel users Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 13/25] crypto: iaa - IAA Batching for parallel compressions/decompressions Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 14/25] crypto: iaa - Enable async mode and make it the default Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 15/25] crypto: iaa - Disable iaa_verify_compress by default Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 16/25] crypto: iaa - Submit the two largest source buffers first in decompress batching Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 17/25] crypto: iaa - Add deflate-iaa-dynamic compression mode Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 18/25] crypto: acomp - Add crypto_acomp_batch_size() to get an algorithm's batch-size Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 19/25] crypto: iaa - IAA acomp_algs register the get_batch_size() interface Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 20/25] mm: zswap: Move the CPU hotplug procedures under "pool functions" Kanchana P Sridhar
2025-07-04 18:39   ` Nhat Pham [this message]
2025-07-04 21:35     ` Sridhar, Kanchana P
2025-07-04  4:23 ` [PATCH v10 21/25] mm: zswap: Per-CPU acomp_ctx resources exist from pool creation to deletion Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 22/25] mm: zswap: Consistently use IS_ERR_OR_NULL() to check acomp_ctx resources Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 23/25] mm: zswap: Allocate pool batching resources if the compressor supports batching Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 24/25] mm: zswap: zswap_store() will process a large folio in batches Kanchana P Sridhar
2025-07-04  4:23 ` [PATCH v10 25/25] mm: zswap: Batched zswap_compress() with compress batching of large folios Kanchana P Sridhar
2025-07-04 18:37 ` [PATCH v10 00/25] zswap compression batching with optimized iaa_crypto driver Nhat Pham
2025-07-04 21:39   ` Sridhar, Kanchana P

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='CAKEwX=PFJzc0pErjMcfeeheGL8u4GWMu2yr-iqWmFvYMKfT3fg@mail.gmail.com' \
    --to=nphamcs@gmail.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=chengming.zhou@linux.dev \
    --cc=clabbe@baylibre.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=senozhatsky@chromium.org \
    --cc=surenb@google.com \
    --cc=usamaarif642@gmail.com \
    --cc=vinicius.gomes@intel.com \
    --cc=vinodh.gopal@intel.com \
    --cc=wajdi.k.feghali@intel.com \
    --cc=ying.huang@linux.alibaba.com \
    --cc=yosry.ahmed@linux.dev \
    /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