From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: david@fromorbit.com, rgoldwyn@suse.de, mhocko@kernel.org
Cc: willy@infradead.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: Removing GFP_NOFS
Date: Sat, 10 Mar 2018 11:44:33 +0900 [thread overview]
Message-ID: <201803101144.IHI87002.MFOtLJOFQVHSFO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20180309223812.GW7000@dastard>
Dave Chinner wrote:
> > OTOH (contradicting myself here), writepages, in essence writebacks, are
> > performed by per-BDI flusher threads which are kicked by the mm code in
> > low memory situations, as opposed to the thread performing the allocation.
> >
> > As Tetsuo pointed out, direct reclaims are the real problematic scenarios.
>
> Sure, but I've been saying for more than 10 years we need to get rid
> of direct reclaim because it's horribly inefficient when there's
> lots of concurrent allocation pressure, not to mention it's full of
> deadlock scenarios like this.
>
> Really, though I'm tired of having the same arguments over and over
> again about architectural problems that people just don't seem to
> understand or want to fix.
>
Yeah, it is sad that developers are not interested in lowmem situation.
Suspect the MM subsystem when your Linux system hung up!?
https://elinux.org/images/4/49/CELFJP-Jamboree63-handa-en.pdf
prev parent reply other threads:[~2018-03-10 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 23:46 Matthew Wilcox
2018-03-09 1:35 ` Dave Chinner
2018-03-09 4:06 ` Dave Chinner
2018-03-09 11:14 ` Tetsuo Handa
2018-03-09 14:48 ` Goldwyn Rodrigues
2018-03-09 22:38 ` Dave Chinner
2018-03-10 2:44 ` Tetsuo Handa [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=201803101144.IHI87002.MFOtLJOFQVHSFO@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rgoldwyn@suse.de \
--cc=willy@infradead.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