From: Andrew Morton <akpm@linux-foundation.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-mm@kvack.org, mhocko@kernel.org, rientjes@google.com,
yosryahmed@google.com, hannes@cmpxchg.org,
almasrymina@google.com, roman.gushchin@linux.dev,
gthelen@google.com, dseo3@uci.edu, a.manzanares@samsung.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] mm: introduce per-node proactive reclaim interface
Date: Wed, 4 Sep 2024 18:15:43 -0700 [thread overview]
Message-ID: <20240904181543.02de2242490cf233c7879697@linux-foundation.org> (raw)
In-Reply-To: <nwutv6cuuyajmakiiznb3hoao6jfhrs2clpqi76xomqbc6yymg@n7inzwjcskhf>
On Wed, 4 Sep 2024 18:08:05 -0700 Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Wed, 04 Sep 2024, Andrew Morton wrote:\n
> >On Wed, 4 Sep 2024 09:27:40 -0700 Davidlohr Bueso <dave@stgolabs.net> wrote:
> >
> >> 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 value per sysfs file is a rule.
>
> I wasn't aware of it as a rule - is this documented somewhere?
Documentation/filesystems/sysfs.rst, line 62. Also lots of gregkh
grumpygrams :)
> I ask because I see some others are using space-separated parameters, ie:
>
> /sys/bus/usb/drivers/foo/new_id
>
> ... or colons. What would be acceptable? echo "512M:10" > ... ?
Kinda cheating. But the rule gets violated a lot.
next prev parent reply other threads:[~2024-09-05 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 16:27 Davidlohr Bueso
2024-09-04 20:18 ` Andrew Morton
2024-09-05 1:08 ` Davidlohr Bueso
2024-09-05 1:15 ` Andrew Morton [this message]
2024-09-05 3:35 ` Davidlohr Bueso
2024-09-05 7:31 ` Yosry Ahmed
2024-09-04 21:29 ` Yosry Ahmed
2024-09-05 21:59 ` Hillf Danton
2024-09-05 23:29 ` Davidlohr Bueso
2024-09-06 11:04 ` Hillf Danton
2024-09-09 7:12 ` Michal Hocko
2024-09-09 10:51 ` Hillf Danton
2024-09-09 14:50 ` Michal Hocko
2024-09-09 7:20 ` Michal Hocko
2024-09-10 16:31 ` Davidlohr Bueso
2024-09-11 6:49 ` Michal Hocko
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=20240904181543.02de2242490cf233c7879697@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.manzanares@samsung.com \
--cc=almasrymina@google.com \
--cc=dave@stgolabs.net \
--cc=dseo3@uci.edu \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--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