From: Joshua Hahn <joshua.hahnjy@gmail.com>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Chengming Zhou <chengming.zhou@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Nhat Pham <nphamcs@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com
Subject: Re: [PATCH] mm/zswap: Remove zswap_pools_counter
Date: Mon, 13 Jan 2025 07:21:29 -0800 [thread overview]
Message-ID: <20250113152132.2372632-1-joshua.hahnjy@gmail.com> (raw)
In-Reply-To: <CAJD7tkaFqMD-JUJ1byV-Udx=ut+fKjtXR=cOqs1ApMEgMXw0bA@mail.gmail.com>
Hi Yosry,
I hope you've had a great start to 2025! (Is it too late to still be doing
New Years greetings? : -))
On Fri, 10 Jan 2025 13:53:06 -0800 Yosry Ahmed <yosryahmed@google.com> wrote:
> On Fri, Jan 10, 2025 at 12:33 PM Joshua Hahn <joshua.hahnjy@gmail.com> wrote:
> >
> > Commit 8edc9c4 [1] reduced the number of pools used by zswap from 32 to 1.
>
> When referring to commits we use the first 12 characters in the SHA1
> and the commit subject, rather than the link (although adding the link
> as well does not hurt). So this should be 'Commit 8edc9c4e72fe
> ("mm/zswap: use only one pool in zswap")'.
Thank you for letting me know. I grabbed the 6-character commit-ID from
Github, but I'll be sure to include the first 12 characters instead in
the future.
> > As such, we no longer need to have unique names for zpool (zsmalloc).
>
> More importantly, I don't think this is accurate. zswap_pools_count
> was introduced by commit 32a4e1690399 ("mm/zswap: provide unique zpool
> name") long before we increased the number of concurrent zpools to 32.
> It is needed because even though we used to have a single zpool per
> zswap_pool (as we returned to doing after [1]), we may have multiple
> zswap_pool's (e.g. if the compressor is changed, a new zswap_pool is
> created).
Ah, thank you for the correction. In retrospect, this was a bit of a
naitve patch, it had completely passed my mind that we can still in fact
have multiple pools at the same time. This could have been avoided if I had
taken a look at where this code was introduced, rather than the patch
that (I thought) removed the last users.
Thank you for the review as always! Have a great day,
Joshua
next prev parent reply other threads:[~2025-01-13 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 20:33 Joshua Hahn
2025-01-10 21:53 ` Yosry Ahmed
2025-01-13 15:21 ` Joshua Hahn [this message]
2025-01-13 16:20 ` Yosry Ahmed
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=20250113152132.2372632-1-joshua.hahnjy@gmail.com \
--to=joshua.hahnjy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@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