From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
iamjoonsoo.kim@lge.com, mhocko@kernel.org, bhe@redhat.com,
mgorman@techsingularity.net, rientjes@google.com
Subject: [PATCH v2 0/3] improvements about lowmem_reserve and /proc/zoneinfo
Date: Thu, 2 Apr 2020 22:01:10 +0800 [thread overview]
Message-ID: <20200402140113.3696-1-bhe@redhat.com> (raw)
In this post, I just drop the patch 4 and patch 5 in old v1 since David
and Michal worried moving per-node stats to the front of /proc/zoneinfo
has potential to break the existing user space scripts. For patch 1~3,
there's no change, seems no risk is found out so far, so just keep them
and repost.
The v1 thread can be found here:
https://lore.kernel.org/linux-mm/20200324142229.12028-1-bhe@redhat.com/
Baoquan He (3):
mm/page_alloc.c: only tune sysctl_lowmem_reserve_ratio value once when
changing it
mm/page_alloc.c: clear out zone->lowmem_reserve[] if the zone is empty
mm/vmstat.c: do not show lowmem reserve protection information of
empty zone
mm/page_alloc.c | 13 +++++++++++--
mm/vmstat.c | 12 ++++++------
2 files changed, 17 insertions(+), 8 deletions(-)
--
2.17.2
next reply other threads:[~2020-04-02 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 14:01 Baoquan He [this message]
2020-04-02 14:01 ` [PATCH v2 1/3] mm/page_alloc.c: only tune sysctl_lowmem_reserve_ratio value once when changing it Baoquan He
2020-04-02 14:01 ` [PATCH v2 2/3] mm/page_alloc.c: clear out zone->lowmem_reserve[] if the zone is empty Baoquan He
2020-04-02 14:01 ` [PATCH v2 3/3] mm/vmstat.c: do not show lowmem reserve protection information of empty zone Baoquan He
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=20200402140113.3696-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=rientjes@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