From: Mel Gorman <mgorman@techsingularity.net>
To: Alexey Avramov <hakavlad@inbox.lv>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Rik van Riel <riel@surriel.com>, Mike Galbraith <efault@gmx.de>,
Darrick Wong <djwong@kernel.org>,
regressions@lists.linux.dev,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] mm: vmscan: Reduce throttling due to a failure to make progress
Date: Thu, 2 Dec 2021 12:15:54 +0000 [thread overview]
Message-ID: <20211202121554.GY3366@techsingularity.net> (raw)
In-Reply-To: <20211202204229.5ed83f31@mail.inbox.lv>
On Thu, Dec 02, 2021 at 08:42:29PM +0900, Alexey Avramov wrote:
> I tested this [1] patch on top of 5.16-rc2, the same tests.
>
Thanks for all the tests you've done for this, it's much appreciated.
> - with noswap:
>
> 2021-12-02 19:41:19,279: Stall times for the last 146.5s:
> 2021-12-02 19:41:19,279: -----------
> 2021-12-02 19:41:19,279: some cpu 1.1s, avg 0.8%
> 2021-12-02 19:41:19,279: -----------
> 2021-12-02 19:41:19,279: some io 116.2s, avg 79.3%
> 2021-12-02 19:41:19,280: full io 109.6s, avg 74.8%
> 2021-12-02 19:41:19,280: -----------
> 2021-12-02 19:41:19,280: some memory 3.9s, avg 2.6%
> 2021-12-02 19:41:19,280: full memory 3.8s, avg 2.6%
>
> Excellent!
>
> psi log:
> https://raw.githubusercontent.com/hakavlad/cache-tests/main/516-reclaim-throttle/516-rc2/patch6/noswap/psi
>
> mem log:
> https://raw.githubusercontent.com/hakavlad/cache-tests/main/516-reclaim-throttle/516-rc2/patch6/noswap/mem
>
> - with swappiness=0
>
> 2021-12-02 19:46:04,860: Stall times for the last 144.5s:
> 2021-12-02 19:46:04,860: -----------
> 2021-12-02 19:46:04,860: some cpu 1.1s, avg 0.8%
> 2021-12-02 19:46:04,860: -----------
> 2021-12-02 19:46:04,860: some io 106.9s, avg 74.0%
> 2021-12-02 19:46:04,861: full io 101.3s, avg 70.1%
> 2021-12-02 19:46:04,861: -----------
> 2021-12-02 19:46:04,861: some memory 99.6s, avg 68.9%
> 2021-12-02 19:46:04,861: full memory 95.6s, avg 66.2%
>
> PSI mem pressure was high, but there were no long stalls.
>
Great, so can I assume you're ok with this version? If yes, can I add
the following?
Tested-by: Alexey Avramov <hakavlad@inbox.lv>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-12-02 12:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:18 [PATCH 1/1] mm: vmscan: Reduce throttling due to a failure to make progress Mel Gorman
2021-11-26 10:14 ` Vlastimil Babka
2021-11-26 10:26 ` Mike Galbraith
2021-11-26 16:12 ` Alexey Avramov
2021-11-26 16:52 ` Mel Gorman
2021-11-27 19:26 ` Alexey Avramov
2021-11-28 10:00 ` Mike Galbraith
2021-11-28 11:39 ` Mike Galbraith
2021-11-28 12:35 ` Mike Galbraith
2021-11-28 18:38 ` Mike Galbraith
2021-11-28 11:58 ` Alexey Avramov
2021-11-29 8:26 ` Mel Gorman
2021-11-29 15:01 ` Mel Gorman
2021-11-30 10:14 ` Mike Galbraith
2021-11-30 11:22 ` Mel Gorman
2021-11-30 12:00 ` Mike Galbraith
2021-11-30 12:51 ` Mike Galbraith
2021-11-30 13:09 ` Mel Gorman
2021-12-01 4:32 ` Mike Galbraith
2021-11-30 16:03 ` Alexey Avramov
2021-11-30 17:27 ` Mel Gorman
2021-11-30 17:59 ` Mike Galbraith
2021-12-01 13:01 ` Mel Gorman
2021-12-01 13:52 ` Mike Galbraith
2021-12-01 15:06 ` Mel Gorman
2021-11-30 18:38 ` Alexey Avramov
2021-12-01 14:00 ` Mel Gorman
2021-12-01 17:29 ` Darrick J. Wong
2021-12-02 9:43 ` Mel Gorman
2021-12-02 16:09 ` Darrick J. Wong
2021-12-02 3:11 ` Mike Galbraith
2021-12-02 10:13 ` Mel Gorman
2021-12-02 10:51 ` Mike Galbraith
2021-12-02 11:42 ` Alexey Avramov
2021-12-02 12:14 ` Alexey Avramov
2021-12-02 12:15 ` Mel Gorman [this message]
2021-12-02 12:22 ` Alexey Avramov
2021-12-02 13:18 Mel Gorman
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=20211202121554.GY3366@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=djwong@kernel.org \
--cc=efault@gmx.de \
--cc=hakavlad@inbox.lv \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=regressions@lists.linux.dev \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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).