linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nhat Pham <nphamcs@gmail.com>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: Barry Song <21cnbao@gmail.com>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Vitaly Wool <vitalywool@gmail.com>,
	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 22:49:57 +0700	[thread overview]
Message-ID: <CAKEwX=MWotmH2YOC-Sdb5Krzt43ogCy8kqJnCLDRm7Db=evDOg@mail.gmail.com> (raw)
In-Reply-To: <CAJD7tkadoYEvCPx6wARTBDseWmroym=H8L60MPgbF5JJX+9OSg@mail.gmail.com>

On Wed, Jan 8, 2025 at 10:36 PM Yosry Ahmed <yosryahmed@google.com> wrote:
>
>
> Oh, I was not talking about my proposed diff, but the existing logic
> that allocates the requests and buffers in the hotplug callbacks
> instead of just using alloc_percpu() to allocate them once for each
> possible CPU. I was wondering if there are actual setups where this
> matters and a significant amount of memory is being saved. Otherwise
> we should simplify things and just rip out the hotplug callbacks.

My vote is for ripping the hotplug callbacks (eventually) :) In
addition to the discrepancy in the number of possible and online CPUs,
we also need a relatively smaller memory size for the discrepancy to
matter, no? Systems with hundreds of CPUs (hopefully) should have
hundreds of GBs worth of memory available (if not more).

Anyhow, we can just go with the diff you sent for now (and for past
kernels). Seems simple enough, and wouldn't get in the way of the
eventual hotplug logic removal (if you decide to pursue it).


  reply	other threads:[~2025-01-08 15:50 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
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 [this message]
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='CAKEwX=MWotmH2YOC-Sdb5Krzt43ogCy8kqJnCLDRm7Db=evDOg@mail.gmail.com' \
    --to=nphamcs@gmail.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chengming.zhou@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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