linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chengming Zhou <chengming.zhou@linux.dev>
To: Nhat Pham <nphamcs@gmail.com>, Yosry Ahmed <yosryahmed@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vitaly Wool <vitalywool@gmail.com>,
	Barry Song <baohua@kernel.org>, Sam Sun <samsun1006219@gmail.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Sridhar, Kanchana P" <kanchana.p.sridhar@intel.com>
Subject: Re: [PATCH v2 2/2] mm: zswap: disable migration while using per-CPU acomp_ctx
Date: Wed, 8 Jan 2025 13:00:24 +0800	[thread overview]
Message-ID: <857acdc4-c4b7-44ea-a67d-2df83ca245ed@linux.dev> (raw)
In-Reply-To: <CAKEwX=OHcZB8Uy5zj8Dhq-ieiwpJFcqRXN_7=mbM1FD_h_uOOA@mail.gmail.com>

On 2025/1/8 12:46, Nhat Pham wrote:
> On Wed, Jan 8, 2025 at 9:34 AM Yosry Ahmed <yosryahmed@google.com> wrote:
>>
>>
>> Actually, using the mutex to protect against CPU hotunplug is not too
>> complicated. The following diff is one way to do it (lightly tested).
>> Johannes, Nhat, any preferences between this patch (disabling
>> migration) and the following diff?
> 
> I mean if this works, this over migration diasbling any day? :)
> 
>>
>> diff --git a/mm/zswap.c b/mm/zswap.c
>> index f6316b66fb236..4d6817c679a54 100644
>> --- a/mm/zswap.c
>> +++ b/mm/zswap.c
>> @@ -869,17 +869,40 @@ 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);
>>
>> +       mutex_lock(&acomp_ctx->mutex);
>>          if (!IS_ERR_OR_NULL(acomp_ctx)) {
>>                  if (!IS_ERR_OR_NULL(acomp_ctx->req))
>>                          acomp_request_free(acomp_ctx->req);
>> +               acomp_ctx->req = NULL;
>>                  if (!IS_ERR_OR_NULL(acomp_ctx->acomp))
>>                          crypto_free_acomp(acomp_ctx->acomp);
>>                  kfree(acomp_ctx->buffer);
>>          }
>> +       mutex_unlock(&acomp_ctx->mutex);
>>
>>          return 0;
>>   }
>>
>> +static struct crypto_acomp_ctx *acomp_ctx_get_cpu_locked(
>> +               struct crypto_acomp_ctx __percpu *acomp_ctx)
>> +{
>> +       struct crypto_acomp_ctx *ctx;
>> +
>> +       for (;;) {
>> +               ctx = raw_cpu_ptr(acomp_ctx);
>> +               mutex_lock(&ctx->mutex);
> 
> I'm a bit confused. IIUC, ctx is per-cpu right? What's protecting this
> cpu-local data (including the mutex) from being invalidated under us
> while we're sleeping and waiting for the mutex?

Yeah, it's not safe, we can only use this_cpu_ptr(), which will disable
preempt (so cpu offline can't kick in), and get refcount of ctx. Since
we can't mutex_lock in the preempt disabled section.

Thanks.

> 
> If it is somehow protected, then yeah this seems quite elegant :)
> 
>> +               if (likely(ctx->req))
>> +                       return ctx;
>> +               /* Raced with zswap_cpu_comp_dead() on CPU hotunplug */
>> +               mutex_unlock(&ctx->mutex);
>> +       }
>> +}
>> +
>> +static void acomp_ctx_put_unlock(struct crypto_acomp_ctx *ctx)
>> +{
>> +       mutex_unlock(&ctx->mutex);
>> +}
>> +
>>   static bool zswap_compress(struct page *page, struct zswap_entry *entry,
>>                             struct zswap_pool *pool)
>>   {
>> @@ -893,10 +916,7 @@ static bool zswap_compress(struct page *page,
>> struct zswap_entry *entry,
>>          gfp_t gfp;
>>          u8 *dst;
>>
>> -       acomp_ctx = raw_cpu_ptr(pool->acomp_ctx);
>> -
>> -       mutex_lock(&acomp_ctx->mutex);
>> -
>> +       acomp_ctx = acomp_ctx_get_cpu_locked(pool->acomp_ctx);
>>          dst = acomp_ctx->buffer;
>>          sg_init_table(&input, 1);
>>          sg_set_page(&input, page, PAGE_SIZE, 0);
>> @@ -949,7 +969,7 @@ static bool zswap_compress(struct page *page,
>> struct zswap_entry *entry,
>>          else if (alloc_ret)
>>                  zswap_reject_alloc_fail++;
>>
>> -       mutex_unlock(&acomp_ctx->mutex);
>> +       acomp_ctx_put_unlock(acomp_ctx);
>>          return comp_ret == 0 && alloc_ret == 0;
>>   }
>>
>> @@ -960,9 +980,7 @@ static void zswap_decompress(struct zswap_entry
>> *entry, struct folio *folio)
>>          struct crypto_acomp_ctx *acomp_ctx;
>>          u8 *src;
>>
>> -       acomp_ctx = raw_cpu_ptr(entry->pool->acomp_ctx);
>> -       mutex_lock(&acomp_ctx->mutex);
>> -
>> +       acomp_ctx = acomp_ctx_get_cpu_locked(entry->pool->acomp_ctx);
>>          src = zpool_map_handle(zpool, entry->handle, ZPOOL_MM_RO);
>>          /*


  reply	other threads:[~2025-01-08  5:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 22:22 [PATCH v2 1/2] Revert "mm: zswap: fix race between [de]compression and CPU hotunplug" Yosry Ahmed
2025-01-07 22:22 ` [PATCH v2 2/2] mm: zswap: disable migration while using per-CPU acomp_ctx Yosry Ahmed
2025-01-07 22:47   ` Barry Song
2025-01-07 23:25     ` Yosry Ahmed
2025-01-07 23:38       ` Barry Song
2025-01-07 23:56         ` Barry Song
2025-01-08  0:01           ` Yosry Ahmed
2025-01-07 23:26     ` Barry Song
2025-01-08  0:01   ` Sridhar, Kanchana P
2025-01-08  0:12     ` Yosry Ahmed
2025-01-08  1:10       ` Sridhar, Kanchana P
2025-01-08  1:18         ` Yosry Ahmed
2025-01-08  2:33           ` Yosry Ahmed
2025-01-08  4:46             ` Nhat Pham
2025-01-08  5:00               ` Chengming Zhou [this message]
2025-01-08  5:34                 ` Yosry Ahmed
2025-01-08  5:55                   ` Yosry Ahmed
2025-01-08  7:56                     ` Barry Song
2025-01-08 15:36                       ` Yosry Ahmed
2025-01-08 15:49                         ` Nhat Pham
2025-01-08 16:17                           ` Yosry Ahmed
2025-01-08  6:00                   ` Chengming Zhou
2025-01-08 15:36                   ` Nhat Pham
2025-01-08  5:06               ` Barry Song
2025-01-08  5:25                 ` Barry Song
2025-01-07 23:01 ` [PATCH v2 1/2] Revert "mm: zswap: fix race between [de]compression and CPU hotunplug" Barry Song
2025-01-07 23:39   ` Yosry Ahmed
2025-01-08  0:34     ` Barry Song
2025-01-08  0:54       ` Yosry Ahmed
2025-01-08  1:11         ` 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=857acdc4-c4b7-44ea-a67d-2df83ca245ed@linux.dev \
    --to=chengming.zhou@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=samsun1006219@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=vitalywool@gmail.com \
    --cc=yosryahmed@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox