| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87qzyfr0u6.fsf@linux.dev>
Date: Wed, 16 Jul 2025 19:46:25 -0700
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: akpm@...ux-foundation.org, mhocko@...nel.org, hannes@...xchg.org,
shakeel.butt@...ux.dev, yosryahmed@...gle.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] mm: introduce per-node proactive reclaim interface
Davidlohr Bueso <dave@...olabs.net> writes:
> This adds support for allowing proactive reclaim in general on a
> NUMA system. A per-node interface extends support for beyond a
> memcg-specific interface, respecting the current semantics of
> memory.reclaim: respecting aging LRU and not supporting
> artificially triggering eviction on nodes belonging to non-bottom
> tiers.
>
> This patch allows userspace to do:
>
> echo "512M swappiness=10" > /sys/devices/system/node/nodeX/reclaim
>
> One of the premises for this is to semantically align as best as
> possible with memory.reclaim. During a brief time memcg did
> support nodemask until 55ab834a86a9 (Revert "mm: add nodes=
> arg to memory.reclaim"), for which semantics around reclaim
> (eviction) vs demotion were not clear, rendering charging
> expectations to be broken.
>
> With this approach:
>
> 1. Users who do not use memcg can benefit from proactive reclaim.
> The memcg interface is not NUMA aware and there are usecases that
> are focusing on NUMA balancing rather than workload memory footprint.
>
> 2. Proactive reclaim on top tiers will trigger demotion, for which
> memory is still byte-addressable. Reclaiming on the bottom nodes
> will trigger evicting to swap (the traditional sense of reclaim).
> This follows the semantics of what is today part of the aging process
> on tiered memory, mirroring what every other form of reclaim does
> (reactive and memcg proactive reclaim). Furthermore per-node proactive
> reclaim is not as susceptible to the memcg charging problem mentioned
> above.
>
> 3. Unlike the nodes= arg, this interface avoids confusing semantics,
> such as what exactly the user wants when mixing top-tier and low-tier
> nodes in the nodemask. Further per-node interface is less exposed to
> "free up memory in my container" usecases, where eviction is intended.
>
> 4. Users that *really* want to free up memory can use proactive reclaim
> on nodes knowingly to be on the bottom tiers to force eviction in a
> natural way - higher access latencies are still better than swap.
> If compelled, while no guarantees and perhaps not worth the effort,
> users could also also potentially follow a ladder-like approach to
> eventually free up the memory. Alternatively, perhaps an 'evict' option
> could be added to the parameters for both memory.reclaim and per-node
> interfaces to force this action unconditionally.
>
> Signed-off-by: Davidlohr Bueso <dave@...olabs.net>
Acked-by: Roman Gushchin <roman.gushchin@...ux.dev>
small nit below
> ---
> Documentation/ABI/stable/sysfs-devices-node | 9 ++++
> drivers/base/node.c | 2 +
> include/linux/swap.h | 16 +++++++
> mm/vmscan.c | 53 ++++++++++++++++++---
> 4 files changed, 74 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/ABI/stable/sysfs-devices-node b/Documentation/ABI/stable/sysfs-devices-node
> index a02707cb7cbc..2d0e023f22a7 100644
> --- a/Documentation/ABI/stable/sysfs-devices-node
> +++ b/Documentation/ABI/stable/sysfs-devices-node
> @@ -227,3 +227,12 @@ Contact: Jiaqi Yan <jiaqiyan@...gle.com>
> Description:
> Of the raw poisoned pages on a NUMA node, how many pages are
> recovered by memory error recovery attempt.
> +
> +What: /sys/devices/system/node/nodeX/reclaim
> +Date: June 2025
> +Contact: Linux Memory Management list <linux-mm@...ck.org>
> +Description:
> + Perform user-triggered proactive reclaim on a NUMA node.
> + This interface is equivalent to the memcg variant.
> +
> + See Documentation/admin-guide/cgroup-v2.rst
> diff --git a/drivers/base/node.c b/drivers/base/node.c
> index 6d66382dae65..548b532a2129 100644
> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -659,6 +659,7 @@ static int register_node(struct node *node, int num)
> } else {
> hugetlb_register_node(node);
> compaction_register_node(node);
> + reclaim_register_node(node);
> }
>
> return error;
> @@ -675,6 +676,7 @@ void unregister_node(struct node *node)
> {
> hugetlb_unregister_node(node);
> compaction_unregister_node(node);
> + reclaim_unregister_node(node);
> node_remove_accesses(node);
> node_remove_caches(node);
> device_unregister(&node->dev);
> diff --git a/include/linux/swap.h b/include/linux/swap.h
> index bc0e1c275fc0..dac7ba98783d 100644
> --- a/include/linux/swap.h
> +++ b/include/linux/swap.h
> @@ -431,6 +431,22 @@ extern unsigned long shrink_all_memory(unsigned long nr_pages);
> extern int vm_swappiness;
> long remove_mapping(struct address_space *mapping, struct folio *folio);
>
> +#if defined(CONFIG_SYSFS) && defined(CONFIG_NUMA)
> +extern int reclaim_register_node(struct node *node);
> +extern void reclaim_unregister_node(struct node *node);
> +
> +#else
> +
> +static inline int reclaim_register_node(struct node *node)
> +{
> + return 0;
> +}
> +
> +static inline void reclaim_unregister_node(struct node *node)
> +{
> +}
> +#endif /* CONFIG_SYSFS && CONFIG_NUMA */
> +
> #ifdef CONFIG_NUMA
> extern int sysctl_min_unmapped_ratio;
> extern int sysctl_min_slab_ratio;
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index cdd9cb97fb79..f77feb75c678 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -94,10 +94,8 @@ struct scan_control {
> unsigned long anon_cost;
> unsigned long file_cost;
>
> -#ifdef CONFIG_MEMCG
> /* Swappiness value for proactive reclaim. Always use sc_swappiness()! */
> int *proactive_swappiness;
> -#endif
>
> /* Can active folios be deactivated as part of reclaim? */
> #define DEACTIVATE_ANON 1
> @@ -121,7 +119,7 @@ struct scan_control {
> /* Has cache_trim_mode failed at least once? */
> unsigned int cache_trim_mode_failed:1;
>
> - /* Proactive reclaim invoked by userspace through memory.reclaim */
> + /* Proactive reclaim invoked by userspace */
> unsigned int proactive:1;
>
> /*
> @@ -7732,13 +7730,15 @@ static const match_table_t tokens = {
> { MEMORY_RECLAIM_NULL, NULL },
> };
>
> -int user_proactive_reclaim(char *buf, struct mem_cgroup *memcg, pg_data_t *pgdat)
> +int user_proactive_reclaim(char *buf,
> + struct mem_cgroup *memcg, pg_data_t *pgdat)
> {
> unsigned int nr_retries = MAX_RECLAIM_RETRIES;
> unsigned long nr_to_reclaim, nr_reclaimed = 0;
> int swappiness = -1;
> char *old_buf, *start;
> substring_t args[MAX_OPT_ARGS];
> + gfp_t gfp_mask = GFP_KERNEL;
>
> if (!buf || (!memcg && !pgdat))
> return -EINVAL;
> @@ -7792,11 +7792,29 @@ int user_proactive_reclaim(char *buf, struct mem_cgroup *memcg, pg_data_t *pgdat
> reclaim_options = MEMCG_RECLAIM_MAY_SWAP |
> MEMCG_RECLAIM_PROACTIVE;
> reclaimed = try_to_free_mem_cgroup_pages(memcg,
> - batch_size, GFP_KERNEL,
> + batch_size, gfp_mask,
> reclaim_options,
> swappiness == -1 ? NULL : &swappiness);
> } else {
> - return -EINVAL;
> + struct scan_control sc = {
> + .gfp_mask = current_gfp_context(gfp_mask),
> + .reclaim_idx = gfp_zone(gfp_mask),
> + .proactive_swappiness = swappiness == -1 ? NULL : &swappiness,
> + .priority = DEF_PRIORITY,
> + .may_writepage = !laptop_mode,
> + .nr_to_reclaim = max(batch_size, SWAP_CLUSTER_MAX),
> + .may_unmap = 1,
> + .may_swap = 1,
> + .proactive = 1,
> + };
> +
> + if (test_and_set_bit_lock(PGDAT_RECLAIM_LOCKED,
> + &pgdat->flags))
> + return -EAGAIN;
Isn't EBUSY a better choice here?
At least to distinguish between no reclaimable memory left and
somebody else is abusing the same interface cases.
Powered by blists - more mailing lists