From: Wupeng Ma <mawupeng1@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <corbet@lwn.net>, <mcgrof@kernel.org>, <keescook@chromium.org>,
<yzaikin@google.com>, <songmuchun@bytedance.com>,
<mike.kravetz@oracle.com>, <osalvador@suse.de>,
<surenb@google.com>, <mawupeng1@huawei.com>, <rppt@kernel.org>,
<charante@codeaurora.org>, <jsavitz@redhat.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>,
<wangkefeng.wang@huawei.com>
Subject: [PATCH -next 0/2] watermark related improvement on zone movable
Date: Thu, 18 Aug 2022 17:04:28 +0800 [thread overview]
Message-ID: <20220818090430.2859992-1-mawupeng1@huawei.com> (raw)
From: Ma Wupeng <mawupeng1@huawei.com>
The first patch cap zone movable's min wmark to small value since no one
can use it.
The second patch introduce a per zone watermark to replace the vanilla
watermark_scale_factor to bring flexibility to tune each zone's
watermark separately and lead to more efficient kswapd.
Each patch's detail information can be seen is its own changelog.
Ma Wupeng (2):
mm: Cap zone movable's min wmark to small value
mm: sysctl: Introduce per zone watermark_scale_factor
Documentation/admin-guide/sysctl/vm.rst | 6 ++++
include/linux/mm.h | 2 +-
include/linux/mmzone.h | 4 +--
kernel/sysctl.c | 2 --
mm/page_alloc.c | 41 +++++++++++++++++++------
5 files changed, 41 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-18 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 9:04 Wupeng Ma [this message]
2022-08-18 9:04 ` [PATCH -next 1/2] mm: Cap zone movable's min wmark to small value Wupeng Ma
2022-08-18 9:04 ` [PATCH -next 2/2] mm: sysctl: Introduce per zone watermark_scale_factor Wupeng Ma
2022-08-18 11:38 ` kernel test robot
2022-08-18 11:49 ` kernel test robot
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=20220818090430.2859992-1-mawupeng1@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=corbet@lwn.net \
--cc=jsavitz@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yzaikin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.