[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3953e198-e9e5-22cc-f196-5d5aca3d7ac1@huawei.com>
Date: Wed, 24 Aug 2022 15:27:16 +0800
From: mawupeng <mawupeng1@...wei.com>
To: <akpm@...ux-foundation.org>
CC: <mawupeng1@...wei.com>, <corbet@....net>, <mcgrof@...nel.org>,
<keescook@...omium.org>, <yzaikin@...gle.com>,
<songmuchun@...edance.com>, <mike.kravetz@...cle.com>,
<osalvador@...e.de>, <rppt@...nel.org>, <surenb@...gle.com>,
<jsavitz@...hat.com>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-fsdevel@...r.kernel.org>, <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH v2 0/2] watermark related improvement on zone movable
Hi, maintainers, kindly ping...
Thanks.
Ma.
On 2022/8/19 17:30, Wupeng Ma wrote:
> From: Ma Wupeng <mawupeng1@...wei.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(-)
>
Powered by blists - more mailing lists