From: Vijay Balakrishna <vijayb@linux.microsoft.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>, Song Liu <songliubraving@fb.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Vijay Balakrishna <vijayb@linux.microsoft.com>,
Michal Hocko <mhocko@suse.com>, Allen Pais <apais@microsoft.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [v3 0/2] recalculate min_free_kbytes post memory hotplug
Date: Wed, 16 Sep 2020 18:21:47 -0700 [thread overview]
Message-ID: <1600305709-2319-1-git-send-email-vijayb@linux.microsoft.com> (raw)
v2 -> v3
--------
[v2 1/2]
- removed symptoms references from changelog
[v2 2/2]
- addressed following issues Michal Hocko raised:
. nr_free_buffer_pages can oveflow in int on very large machines
. min_free_kbytes can decrease the size theoretically
v1 -> v2
--------
- addressed issue Kirill A. Shutemov raised:
. changes would override min_free_kbytes set by user
Vijay Balakrishna (2):
mm: khugepaged: recalculate min_free_kbytes after memory hotplug as
expected by khugepaged
mm: khugepaged: avoid overriding min_free_kbytes set by user
include/linux/khugepaged.h | 5 +++++
mm/khugepaged.c | 16 +++++++++++++---
mm/memory_hotplug.c | 3 +++
mm/page_alloc.c | 2 +-
4 files changed, 22 insertions(+), 4 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-17 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 1:21 Vijay Balakrishna [this message]
2020-09-17 1:21 ` [v3 1/2] mm: khugepaged: recalculate min_free_kbytes after memory hotplug as expected by khugepaged Vijay Balakrishna
2020-09-21 12:55 ` Sasha Levin
2020-09-23 21:27 ` Vijay Balakrishna
2020-09-25 2:51 ` Andrew Morton
2020-09-25 7:45 ` Michal Hocko
2020-09-25 7:42 ` Michal Hocko
2020-09-25 16:31 ` Vijay Balakrishna
2020-09-17 1:21 ` [v3 2/2] mm: khugepaged: avoid overriding min_free_kbytes set by user Vijay Balakrishna
2020-09-17 4:22 ` Vijay Balakrishna
2020-09-21 12:54 ` Sasha Levin
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=1600305709-2319-1-git-send-email-vijayb@linux.microsoft.com \
--to=vijayb@linux.microsoft.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apais@microsoft.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=songliubraving@fb.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).