From: Mel Gorman <mgorman@techsingularity.net>
To: Shuang Zhai <szhai2@cs.rochester.edu>
Cc: akpm@linux-foundation.org, djwong@kernel.org, efault@gmx.de,
hakavlad@inbox.lv, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mhocko@suse.com, regressions@lists.linux.dev, riel@surriel.com,
vbabka@suse.cz
Subject: Re: [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress'
Date: Wed, 23 Feb 2022 12:50:02 +0000 [thread overview]
Message-ID: <20220223125002.GE4423@techsingularity.net> (raw)
In-Reply-To: <20220222172731.31949-1-szhai2@cs.rochester.edu>
On Tue, Feb 22, 2022 at 12:27:31PM -0500, Shuang Zhai wrote:
> Mel Gorman wrote:
> > On Mon, Feb 14, 2022 at 04:10:50PM -0500, Shuang Zhai wrote:
> > > Hi Mel,
> > >
> > > Mel Gorman wrote:
> > > >
> > > > Mike Galbraith, Alexey Avramov and Darrick Wong all reported similar
> > > > problems due to reclaim throttling for excessive lengths of time.
> > > > In Alexey's case, a memory hog that should go OOM quickly stalls for
> > > > several minutes before stalling. In Mike and Darrick's cases, a small
> > > > memcg environment stalled excessively even though the system had enough
> > > > memory overall.
> > > >
> > >
> > > I recently found a regression when I tested MGLRU with fio on Linux
> > > 5.16-rc6 [1]. After this patch was applied, I re-ran the test with Linux
> > > 5.16, but the regression has not been fixed yet.
> > >
> >
> > Am I correct in thinging that this only happens with MGLRU?
>
> Sorry about the confusion and let me clarify on this. The regression happens
> on upstream Linux with the default page replacement mechanism.
Ok, the fio command for me simply exits with an error and even if it didn't
the test machine I have with persistent memory does not have enough pmem
to trigger memory reclaim issues with fio. Can you do the following please?
# echo 1 > vmscan/mm_vmscan_throttled/enable
# cat /sys/kernel/debug/tracing/trace_pipe > trace.out
and run the test? Compress trace.out with xz and send it to me by mail.
If the trace is too large, send as much as you can.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2022-02-23 12:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:06 [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress Mel Gorman
2021-12-02 16:30 ` Shakeel Butt
2021-12-02 16:52 ` Mel Gorman
2021-12-02 17:41 ` Shakeel Butt
2021-12-03 9:01 ` Mel Gorman
2021-12-03 17:50 ` Shakeel Butt
2021-12-03 19:08 ` Mel Gorman
2021-12-06 6:06 ` Shakeel Butt
2021-12-06 11:25 ` Mel Gorman
2021-12-07 7:14 ` Shakeel Butt
2021-12-07 9:28 ` Mel Gorman
2021-12-09 6:20 ` Hugh Dickins
2021-12-09 9:53 ` Mel Gorman
2021-12-28 10:04 ` Thorsten Leemhuis
2021-12-29 23:45 ` Andrew Morton
2021-12-31 14:24 ` Thorsten Leemhuis
2021-12-31 18:33 ` Hugh Dickins
2021-12-31 19:14 ` Linus Torvalds
2021-12-31 19:21 ` Linus Torvalds
2021-12-31 19:22 ` Linus Torvalds
2022-01-01 10:52 ` Thorsten Leemhuis
2021-12-31 21:04 ` Andrew Morton
2021-12-31 21:18 ` Linus Torvalds
2022-02-14 21:10 ` Shuang Zhai
2022-02-15 14:49 ` Mel Gorman
2022-02-22 17:27 ` [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress' Shuang Zhai
2022-02-23 12:50 ` Mel Gorman [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=20220223125002.GE4423@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=szhai2@cs.rochester.edu \
--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).