From: mawupeng <mawupeng1@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <mawupeng1@huawei.com>, <corbet@lwn.net>, <mcgrof@kernel.org>,
<keescook@chromium.org>, <yzaikin@google.com>,
<songmuchun@bytedance.com>, <mike.kravetz@oracle.com>,
<osalvador@suse.de>, <rppt@kernel.org>, <surenb@google.com>,
<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: Re: [PATCH v2 0/2] watermark related improvement on zone movable
Date: Wed, 24 Aug 2022 15:27:16 +0800 [thread overview]
Message-ID: <3953e198-e9e5-22cc-f196-5d5aca3d7ac1@huawei.com> (raw)
In-Reply-To: <20220819093025.105403-1-mawupeng1@huawei.com>
Hi, maintainers, kindly ping...
Thanks.
Ma.
On 2022/8/19 17:30, Wupeng Ma wrote:
> From: Ma Wupeng <mawupeng1@huawei.com>
>
> The first patch cap zone movable's min watermark 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.
>
> changelog since v1:
> - fix compile error if CONFIG_SYSCTL is not enabled
> - remove useless function comment
>
> 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 +-
> kernel/sysctl.c | 2 --
> mm/page_alloc.c | 41 +++++++++++++++++++------
> 4 files changed, 39 insertions(+), 12 deletions(-)
>
prev parent reply other threads:[~2022-08-24 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:30 Wupeng Ma
2022-08-19 9:30 ` [PATCH v2 1/2] mm: Cap zone movable's min wmark to small value Wupeng Ma
2022-08-24 8:10 ` David Hildenbrand
2022-08-25 0:49 ` mawupeng
2022-08-19 9:30 ` [PATCH v2 2/2] mm: sysctl: Introduce per zone watermark_scale_factor Wupeng Ma
2022-08-24 7:27 ` mawupeng [this message]
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=3953e198-e9e5-22cc-f196-5d5aca3d7ac1@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox