linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Wupeng Ma <mawupeng1@huawei.com>
Cc: akpm@linux-foundation.org, david@redhat.com, npiggin@suse.de,
	ying.huang@intel.com, hannes@cmpxchg.org, corbet@lwn.net,
	mcgrof@kernel.org, mgorman@suse.de, keescook@chromium.org,
	yzaikin@google.com, songmuchun@bytedance.com,
	mike.kravetz@oracle.com, osalvador@suse.de, surenb@google.com,
	rppt@kernel.org, charante@codeaurora.org, jsavitz@redhat.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH -next v3 2/2] mm: sysctl: Introduce per zone watermark_scale_factor
Date: Mon, 5 Sep 2022 04:45:06 +0100	[thread overview]
Message-ID: <YxVwwndLt+bsUDK0@casper.infradead.org> (raw)
In-Reply-To: <20220905032858.1462927-3-mawupeng1@huawei.com>

On Mon, Sep 05, 2022 at 11:28:58AM +0800, Wupeng Ma wrote:
> The reason to disable THP is khugepaged_min_free_kbytes_update() will
> update min watermark.
> 
> Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
> Reported-by: kernel test robot <lkp@intel.com>

Don't include this 'Reported-by'.  The kernel test robot did not
tell you to write this patch.


  reply	other threads:[~2022-09-05  3:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  3:28 [PATCH -next v3 0/2] watermark related improvement on zone movable Wupeng Ma
2022-09-05  3:28 ` [PATCH -next v3 1/2] mm: Cap zone movable's min wmark to small value Wupeng Ma
2022-09-05  9:26   ` Mel Gorman
2022-09-06 10:12     ` mawupeng
2022-09-06 12:22       ` Mel Gorman
2022-09-07  8:42         ` mawupeng
2022-09-05  3:28 ` [PATCH -next v3 2/2] mm: sysctl: Introduce per zone watermark_scale_factor Wupeng Ma
2022-09-05  3:45   ` Matthew Wilcox [this message]
2022-09-05  6:39     ` mawupeng
2022-09-06 18:23   ` Luis Chamberlain
2022-09-07  3:29     ` mawupeng
2022-09-09 21:41   ` Khalid Aziz
2022-09-13  2:09     ` mawupeng
2022-09-14 22:42       ` Khalid Aziz

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=YxVwwndLt+bsUDK0@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=charante@codeaurora.org \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=jsavitz@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mawupeng1@huawei.com \
    --cc=mcgrof@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mike.kravetz@oracle.com \
    --cc=npiggin@suse.de \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=songmuchun@bytedance.com \
    --cc=surenb@google.com \
    --cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).