From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mina Almasry <almasrymina@google.com>,
Huang Ying <ying.huang@intel.com>,
Yang Shi <yang.shi@linux.alibaba.com>,
Yosry Ahmed <yosryahmed@google.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
weixugc@google.com, shakeelb@google.com, gthelen@google.com,
fvdl@google.com, Tejun Heo <tj@kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v2] mm: Add nodes= arg to memory.reclaim
Date: Wed, 30 Nov 2022 15:44:11 +0700 [thread overview]
Message-ID: <7c5e0ca5-0ad1-452d-60b9-50dbb63d2dee@gmail.com> (raw)
In-Reply-To: <20221130020328.1009347-1-almasrymina@google.com>
On 11/30/22 09:03, Mina Almasry wrote:
> - This file accepts a single key, the number of bytes to reclaim.
> - No nested keys are currently supported.
> + This file accepts a string which contains the number of bytes to
> + reclaim.
>
Amount of memory to reclaim?
> + This file also allows the user to specify the nodes to reclaim from,
> + via the 'nodes=' key, example::
> +
"..., for example"
> + echo "1G nodes=0,1" > memory.reclaim
> +
> + The above instructs the kernel to reclaim memory from nodes 0,1.
> +
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-11-30 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:03 [RFC PATCH v2] mm: Add nodes= arg to memory.reclaim Mina Almasry
2022-11-30 8:44 ` Bagas Sanjaya [this message]
2022-11-30 19:45 ` Mina Almasry
2022-12-01 14:49 ` Michal Hocko
2022-12-01 21:32 ` Shakeel Butt
2022-12-01 22:10 ` Mina Almasry
2022-12-02 6:04 ` Muchun Song
2022-12-02 6:24 ` Mina Almasry
2022-12-02 3:25 ` Huang, Ying
2022-12-02 4:32 ` Mina Almasry
2022-12-05 1:45 ` Huang, Ying
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=7c5e0ca5-0ad1-452d-60b9-50dbb63d2dee@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=fvdl@google.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=tim.c.chen@linux.intel.com \
--cc=tj@kernel.org \
--cc=weixugc@google.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).