From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Tetsuo Handa" <penguin-kernel@I-love.SAKURA.ne.jp>,
"Tejun Heo" <tj@kernel.org>,
"Cristopher Lameter" <clameter@sgi.com>,
"Arkadiusz Miśkiewicz" <arekm@maven.pl>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
"Joonsoo Kim" <js1304@gmail.com>,
"Christoph Lameter" <cl@linux.com>
Subject: Re: [PATCH] mm, vmstat: Allow WQ concurrency to discover memory reclaim doesn't make any progress
Date: Wed, 25 Nov 2015 14:12:33 -0800 [thread overview]
Message-ID: <20151125141233.aa6dcb1a35527a363cb0776a@linux-foundation.org> (raw)
In-Reply-To: <20151125110705.GC27283@dhcp22.suse.cz>
On Wed, 25 Nov 2015 12:07:05 +0100 Michal Hocko <mhocko@kernel.org> wrote:
> On Tue 24-11-15 15:44:48, Andrew Morton wrote:
> [...]
> > > Even though we haven't seen bug reports in the past I would suggest
> > > backporting this to the stable trees. The issue is present since we have
> > > stopped useing congestion_wait in the retry loop because WQ concurrency
> > > is older as well as vmstat worqueue based refresh AFAICS.
> >
> > hm, I'm reluctant. If the patch fixes something that real people are
> > really hurting from then yes. But I suspect this is just one fly-swat
> > amongst many.
>
> Arkadiusz was seeing reclaim issues [1] on 4.1 kernel. I didn't have
> time to look deeper in that report but vmstat counters seemed terribly
> outdated and the issue went away when this patch was used. The thing is
> that there were others in the bundle so it is not 100% clear whether the
> patch alone helped or it was just a part of the puzzle.
>
> Anyway I think that the issue is not solely theoretical. WQ_MEM_RECLAIM
> is simply not working if the allocation path doesn't sleep currently and
> my understanding of what Tejun claims [2] is that that reimplementing WQ
> concurrency would be too intrusive and lacks sufficient justification
> because other kernel paths do sleep. This patch tries to reduce the
> sleep only to worker threads which should not cause any problems to
> regular tasks.
>
> I am open to any other suggestions. I do not like artificial sleep as
> well but this sounds like the most practical way to go now.
>
> [1] http://lkml.kernel.org/r/201511102313.36685.arekm@maven.pl
> [2] http://lkml.kernel.org/r/20151106001648.GA18183@mtj.duckdns.org
hmpf, OK, I stuck a cc:stable in there. It looks like the current
changelog is sufficient to explain to Greg (and others) why we think
backporting is needed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-11-25 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 12:30 Michal Hocko
2015-11-24 10:42 ` Michal Hocko
2015-11-24 10:54 ` [PATCH] mm, vmstat: Allow WQ concurrency to discover memoryreclaim " Tetsuo Handa
2015-11-24 23:44 ` [PATCH] mm, vmstat: Allow WQ concurrency to discover memory reclaim " Andrew Morton
2015-11-25 2:44 ` Joonsoo Kim
2015-11-25 11:07 ` Michal Hocko
2015-11-25 11:54 ` Tetsuo Handa
2015-11-25 22:12 ` Andrew Morton [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=20151125141233.aa6dcb1a35527a363cb0776a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=cl@linux.com \
--cc=clameter@sgi.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tj@kernel.org \
/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