linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: liwenyu <wenyuli@ex.bilibili.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bsingharora@gmail.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, wangyun@bilibili.com
Subject: Re: [PATCH] delayacct: add memory reclaim delay in get_page_from_freelist
Date: Mon, 25 Sep 2023 14:43:36 +0800	[thread overview]
Message-ID: <9F7DFA20B598B0C4+7dc938b0-67f9-422a-8051-3a7c1fd7a6bf@ex.bilibili.com> (raw)
In-Reply-To: <20230920090711.ecc2d84cc29bb0fa540f1999@linux-foundation.org>


> On Wed, 20 Sep 2023 17:38:49 +0800 liwenyu <wenyuli@ex.bilibili.com> wrote:
> 
>> The current memory reclaim delay statistics only count the direct memory
>> reclaim of the task in do_try_to_free_pages(). In systems with NUMA
>> open, some tasks occasionally experience slower response times, but the
>> total count of reclaim does not increase, using ftrace can show that
>> node_reclaim has occurred.
>>
>> The memory reclaim occurring in get_page_from_freelist() is also due to
>> heavy memory load. To get the impact of tasks in memory reclaim, this
>> patch adds the statistics of the memory reclaim delay statistics for
>> __node_reclaim().
> 
> Please review Documentation/accounting/delay-accounting.rst, see if
> there is some change we can make to reflect this patch.
> 
> Your email client is wordwrapping the patches - please check that for
> next time.
> 

There is no need to change the 
Documentation/accounting/delay-accounting.rst, because this patch is 
only an expansion of  memory reclaim delayacct.

Thanks!



      reply	other threads:[~2023-09-25  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  9:38 liwenyu
2023-09-20 16:07 ` Andrew Morton
2023-09-25  6:43   ` liwenyu [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=9F7DFA20B598B0C4+7dc938b0-67f9-422a-8051-3a7c1fd7a6bf@ex.bilibili.com \
    --to=wenyuli@ex.bilibili.com \
    --cc=akpm@linux-foundation.org \
    --cc=bsingharora@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wangyun@bilibili.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