From: Education Directorate <bsingharora@gmail.com>
To: "liwenyu01@bilibili.com" <liwenyu01@bilibili.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wangyun@bilibili.com" <wangyun@bilibili.com>
Subject: Re: [PATCH RFC] delayacct: add memory reclaim delay in get_page_from_freelist
Date: Wed, 6 Sep 2023 10:53:11 +1000 [thread overview]
Message-ID: <ZPfNdzXCqSx2mV6m@balbir-desktop> (raw)
In-Reply-To: <SH0PR01MB0587592CA2974791B177BFA4C1E8A@SH0PR01MB0587.CHNPR01.prod.partner.outlook.cn>
On Tue, Sep 05, 2023 at 05:32:15AM +0000, liwenyu01@bilibili.com wrote:
> >> 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().
> >>
> >> ...
> >>
> >> --- a/mm/vmscan.c
> >> +++ b/mm/vmscan.c
> >> @@ -8010,6 +8010,7 @@ static int __node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned in
> >>
> >> cond_resched();
> >> psi_memstall_enter(&pflags);
> >> + delayacct_freepages_start();
> >> fs_reclaim_acquire(sc.gfp_mask);
> >> /*
> >> * We need to be able to allocate from the reserves for RECLAIM_UNMAP
> >> @@ -8032,6 +8033,7 @@ static int __node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned in
> >> memalloc_noreclaim_restore(noreclaim_flag);
> >> fs_reclaim_release(sc.gfp_mask);
> >> psi_memstall_leave(&pflags);
> >> + delayacct_freepages_end();
> >>
> >> trace_mm_vmscan_node_reclaim_end(sc.nr_reclaimed);
> >
> > __node_reclaim() calls shrink_node() which at some point will call
> > do_try_to_free_pages() (yes?), which calls delayacct_freepages_start().
> >
> > So we're effectively nesting calls to delayacct_freepages_start(),
> > which isn't designed for that?
> >
> sorry, the last reply was a mistake.
>
> It seems that no point in shrink_node() will call do_try_to_free_pages().
> And do_try_to_free_pages() will call shrink_node() through shrink_zones(),
> if shrink_node() also has some point will call do_try_to_free_pages,then
> delayacct_freepages_start() is nested now?
That's because shrink_node() goes through shrink_list() via
shrink_lruvec()? do_try_to_free_pages() will call shrink_node(). Ideally
we should have some counters around __node_reclaim() and balance_pgdat()
like psi_memstall_* does. Do you want to mimic what psi_memstall_* does?
This would change the definition of delayacct free pages, but I don't think
it will make it worse.
Balbir Singh
next prev parent reply other threads:[~2023-09-06 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 9:54 liwenyu01
2023-08-31 7:26 ` liwenyu01
2023-09-02 23:44 ` Andrew Morton
2023-09-05 2:56 ` 答复: [External]Re: " liwenyu01
2023-09-05 5:32 ` liwenyu01
2023-09-06 0:53 ` Education Directorate [this message]
2023-09-07 11:52 ` liwenyu01
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=ZPfNdzXCqSx2mV6m@balbir-desktop \
--to=bsingharora@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwenyu01@bilibili.com \
--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