From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mgorman@suse.de,
dave.hansen@intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: How to make warn_alloc() reliable?
Date: Thu, 20 Oct 2016 21:30:34 +0200 [thread overview]
Message-ID: <20161020193034.GD27342@dhcp22.suse.cz> (raw)
In-Reply-To: <201610202107.FBC86440.SVFHFtOFOOLQJM@I-love.SAKURA.ne.jp>
On Thu 20-10-16 21:07:49, Tetsuo Handa wrote:
[...]
> By the way, regarding "making the direct reclaim path more deterministic"
> part, I wish that we can
>
> (1) introduce phased watermarks which varies based on stage of reclaim
> operation (e.g. watermark_lower()/watermark_higher() which resembles
> preempt_disable()/preempt_enable() but is propagated to other threads
> when delegating operations needed for reclaim to other threads).
>
> (2) introduce dedicated kernel threads which perform only specific
> reclaim operation, using watermark propagated from other threads
> which performs different reclaim operation.
>
> (3) remove direct reclaim which bothers callers with managing correct
> GFP_NOIO / GFP_NOFS / GFP_KERNEL distinction. Then, normal
> ___GFP_DIRECT_RECLAIM callers can simply wait for
> wait_event(get_pages_from_freelist() succeeds) rather than polling
> with complicated short sleep. This will significantly save CPU
> resource (especially when oom_lock is held) which is wasted by
> activities by multiple concurrent direct reclaim.
As always, you are free to come up with patches with the proper
justification and convince people that those steps will help both the
regular case as well of those you are bothered with.
--
Michal Hocko
SUSE Labs
--
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:[~2016-10-20 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 11:04 How to make warn_alloc() reliable? Tetsuo Handa
2016-10-18 12:27 ` Michal Hocko
2016-10-19 11:27 ` Tetsuo Handa
2016-10-19 11:55 ` Michal Hocko
2016-10-20 12:07 ` Tetsuo Handa
2016-10-20 19:30 ` Michal Hocko [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=20161020193034.GD27342@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).