From: David Hildenbrand <david@redhat.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>,
akpm@linux-foundation.org, mhocko@kernel.org, hannes@cmpxchg.org,
shakeelb@google.com, vdavydov.dev@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Allocate shrinker_map on appropriate NUMA node
Date: Fri, 31 Jan 2020 15:57:07 +0100 [thread overview]
Message-ID: <ebe1c944-2e0f-136d-dd09-0bb37d500fe2@redhat.com> (raw)
In-Reply-To: <158047248934.390127.5043060848569612747.stgit@localhost.localdomain>
On 31.01.20 13:09, Kirill Tkhai wrote:
> Despite shrinker_map may be touched from any cpu
> (e.g., a bit there may be set by a task running
> everywhere); kswapd is always bound to specific
> node. So, we will allocate shrinker_map from
> related NUMA node to respect its NUMA locality.
> Also, this follows generic way we use for allocation
> memcg's per-node data.
>
> Two hunks node_state() patterns are borrowed from
> alloc_mem_cgroup_per_node_info().
>
> Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
> ---
> mm/memcontrol.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 6f6dc8712e39..8ccc8ceb1b17 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -323,7 +323,7 @@ static int memcg_expand_one_shrinker_map(struct mem_cgroup *memcg,
> int size, int old_size)
> {
> struct memcg_shrinker_map *new, *old;
> - int nid;
> + int nid, tmp;
>
> lockdep_assert_held(&memcg_shrinker_map_mutex);
>
> @@ -333,8 +333,9 @@ static int memcg_expand_one_shrinker_map(struct mem_cgroup *memcg,
> /* Not yet online memcg */
> if (!old)
> return 0;
> -
> - new = kvmalloc(sizeof(*new) + size, GFP_KERNEL);
> + /* See comment in alloc_mem_cgroup_per_node_info()*/
> + tmp = node_state(nid, N_NORMAL_MEMORY) ? nid : - 1;
> + new = kvmalloc_node(sizeof(*new) + size, GFP_KERNEL, tmp);
> if (!new)
> return -ENOMEM;
>
> @@ -370,7 +371,7 @@ static void memcg_free_shrinker_maps(struct mem_cgroup *memcg)
> static int memcg_alloc_shrinker_maps(struct mem_cgroup *memcg)
> {
> struct memcg_shrinker_map *map;
> - int nid, size, ret = 0;
> + int nid, size, tmp, ret = 0;
>
> if (mem_cgroup_is_root(memcg))
> return 0;
> @@ -378,7 +379,9 @@ static int memcg_alloc_shrinker_maps(struct mem_cgroup *memcg)
> mutex_lock(&memcg_shrinker_map_mutex);
> size = memcg_shrinker_map_size;
> for_each_node(nid) {
> - map = kvzalloc(sizeof(*map) + size, GFP_KERNEL);
> + /* See comment in alloc_mem_cgroup_per_node_info()*/
> + tmp = node_state(nid, N_NORMAL_MEMORY) ? nid : - 1;
> + map = kvzalloc_node(sizeof(*map) + size, GFP_KERNEL, tmp);
> if (!map) {
> memcg_free_shrinker_maps(memcg);
> ret = -ENOMEM;
>
I think it is preferred to use NUMA_NO_NODE instead of -1.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-01-31 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 12:09 Kirill Tkhai
2020-01-31 14:57 ` David Hildenbrand [this message]
2020-01-31 15:00 ` [PATCH v2] " Kirill Tkhai
2020-01-31 15:47 ` Michal Hocko
2020-01-31 15:49 ` Kirill Tkhai
2020-01-31 16:01 ` Michal Hocko
2020-01-31 16:08 ` [PATCH v3] " Kirill Tkhai
2020-01-31 16:18 ` Michal Hocko
2020-02-03 9:31 ` Kirill Tkhai
2020-01-31 16:20 ` David Hildenbrand
2020-01-31 17:22 ` Shakeel Butt
2020-01-31 22:37 ` Roman Gushchin
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=ebe1c944-2e0f-136d-dd09-0bb37d500fe2@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
--cc=vdavydov.dev@gmail.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