From: Johannes Weiner <hannes@cmpxchg.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nhat Pham <nphamcs@gmail.com>,
Chengming Zhou <chengming.zhou@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] mm: zswap: calculate limits only when updated
Date: Fri, 5 Apr 2024 11:26:19 -0400 [thread overview]
Message-ID: <20240405152619.GA866431@cmpxchg.org> (raw)
In-Reply-To: <20240405053510.1948982-3-yosryahmed@google.com>
On Fri, Apr 05, 2024 at 05:35:07AM +0000, Yosry Ahmed wrote:
> Currently, we calculate the zswap global limit, and potentially the
> acceptance threshold in the zswap, in pages in the zswap store path.
> This is unnecessary because the values rarely change.
>
> Instead, precalculate the them when the module parameters are updated,
> which should be rare. Since we are adding custom handlers for setting
> the percentages now, add proper validation that they are <= 100.
>
> Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
Nice! Getting that stuff out of the hotpath!
Two comments below:
> @@ -684,6 +703,43 @@ static int zswap_enabled_param_set(const char *val,
> return ret;
> }
>
> +static int __zswap_percent_param_set(const char *val,
> + const struct kernel_param *kp)
> +{
> + unsigned int n;
> + int ret;
> +
> + ret = kstrtouint(val, 10, &n);
> + if (ret || n > 100)
> + return -EINVAL;
> +
> + return param_set_uint(val, kp);
> +}
> +
> +static int zswap_max_pool_param_set(const char *val,
> + const struct kernel_param *kp)
> +{
> + int err = __zswap_percent_param_set(val, kp);
> +
> + if (!err) {
> + zswap_update_max_pages();
> + zswap_update_accept_thr_pages();
> + }
> +
> + return err;
> +}
> +
> +static int zswap_accept_thr_param_set(const char *val,
> + const struct kernel_param *kp)
> +{
> + int err = __zswap_percent_param_set(val, kp);
> +
> + if (!err)
> + zswap_update_accept_thr_pages();
> +
> + return err;
> +}
I think you can keep this simple and just always update both if
anything changes for whatever reason. It's an extremely rare event
after all. That should cut it from 3 functions to 1.
Note that totalram_pages can also change during memory onlining and
offlining. For that you need a memory notifier that also calls that
refresh function. It's simple enough, though, check out the code
around register_memory_notifier() in drivers/xen/balloon.c.
next prev parent reply other threads:[~2024-04-05 15:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 5:35 [PATCH v2 0/5] zswap same-filled and limit checking cleanups Yosry Ahmed
2024-04-05 5:35 ` [PATCH v2 1/5] mm: zswap: always shrink in zswap_store() if zswap_pool_reached_full Yosry Ahmed
2024-04-05 5:35 ` [PATCH v2 2/5] mm: zswap: calculate limits only when updated Yosry Ahmed
2024-04-05 15:26 ` Johannes Weiner [this message]
2024-04-05 18:43 ` Yosry Ahmed
2024-04-08 7:54 ` David Hildenbrand
2024-04-08 8:07 ` Yosry Ahmed
2024-04-09 19:32 ` David Hildenbrand
2024-04-10 0:52 ` Yosry Ahmed
2024-04-12 19:48 ` David Hildenbrand
2024-04-13 1:05 ` Yosry Ahmed
2024-04-15 15:10 ` David Hildenbrand
2024-04-15 18:30 ` Yosry Ahmed
2024-04-15 19:15 ` David Hildenbrand
2024-04-15 19:17 ` Yosry Ahmed
2024-04-05 20:23 ` kernel test robot
2024-04-05 20:29 ` Yosry Ahmed
2024-04-05 5:35 ` [PATCH v2 3/5] mm: zswap: refactor limit checking from zswap_store() Yosry Ahmed
2024-04-05 19:57 ` Nhat Pham
2024-04-10 2:30 ` Chengming Zhou
2024-04-05 5:35 ` [PATCH v2 4/5] mm: zswap: move more same-filled pages checks outside of zswap_store() Yosry Ahmed
2024-04-05 5:35 ` [PATCH v2 5/5] mm: zswap: remove same_filled module params Yosry Ahmed
2024-04-05 19:58 ` Nhat Pham
2024-04-10 2:31 ` Chengming Zhou
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=20240405152619.GA866431@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--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