From: David Hildenbrand <david@redhat.com>
To: Charan Teja Reddy <charante@codeaurora.org>,
akpm@linux-foundation.org, rientjes@google.com, vbabka@suse.cz,
mhocko@suse.com, mgorman@techsingularity.net, linux-mm@kvack.org
Cc: vinmenon@codeaurora.org, sudaraja@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/1] mm: balancing the node zones occupancy
Date: Thu, 18 Feb 2021 19:16:30 +0100 [thread overview]
Message-ID: <82e0e9c2-8187-8e2f-0d5e-304dafcda017@redhat.com> (raw)
In-Reply-To: <cover.1613661472.git.charante@codeaurora.org>
On 18.02.21 18:24, Charan Teja Reddy wrote:
> I would like to start discussion about balancing the occupancy of
> memory zones in a node in the system whose imabalance may be caused by
> migration of pages to other zones during hotremove and then hotadding
> same memory. In this case there is a lot of free memory in newly hotadd
> memory which can be filled up by the previous migrated pages(as part of
> offline/hotremove) thus may free up some pressure in other zones of the
> node.
Why is this specific to memory hot(un)plug? I think the problem is more
generic:
Assume
1. Application 1 allocates a lot of memory and gets ZONE_MOVABLE.
2. Application 2 allocates a lot of memory and gets ZONE_NORMAL.
3. Application 1 quits.
Same problem, no?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-02-18 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 17:24 [PATCH RFC 0/1] mm: balancing the node zones occupancy Charan Teja Reddy
2021-02-18 17:24 ` [PATCH 1/1] mm: proof-of-concept for balancing " Charan Teja Reddy
2021-02-18 18:16 ` David Hildenbrand [this message]
2021-02-23 12:30 ` [PATCH RFC 0/1] mm: balancing the " Charan Teja Kalla
2021-02-19 11:26 ` Vlastimil Babka
2021-02-23 13:45 ` Charan Teja Kalla
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=82e0e9c2-8187-8e2f-0d5e-304dafcda017@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=sudaraja@codeaurora.org \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
/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).