From: Johannes Weiner <hannes@cmpxchg.org>
To: mhocko@kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves
Date: Wed, 11 Nov 2015 10:54:46 -0500 [thread overview]
Message-ID: <20151111155446.GA24431@cmpxchg.org> (raw)
In-Reply-To: <1447249697-13380-1-git-send-email-mhocko@kernel.org>
On Wed, Nov 11, 2015 at 02:48:17PM +0100, mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> __GFP_NOFAIL is a big hammer used to ensure that the allocation
> request can never fail. This is a strong requirement and as such
> it also deserves a special treatment when the system is OOM. The
> primary problem here is that the allocation request might have
> come with some locks held and the oom victim might be blocked
> on the same locks. This is basically an OOM deadlock situation.
>
> This patch tries to reduce the risk of such a deadlocks by giving
> __GFP_NOFAIL allocations a special treatment and let them dive into
> memory reserves after oom killer invocation. This should help them
> to make a progress and release resources they are holding. The OOM
> victim should compensate for the reserves consumption.
>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
>
> Hi,
> this has been posted previously as a part of larger GFP_NOFS related
> patch set (http://lkml.kernel.org/r/1438768284-30927-1-git-send-email-mhocko%40kernel.org)
> but Andrea was asking basically the same thing at LSF early this year
> (I cannot seem to find it in any public archive though). I think the
> patch makes some sense on its own.
I sent this right after LSF based on Andrea's suggestion:
https://lkml.org/lkml/2015/3/25/37
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: mhocko@kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves
Date: Wed, 11 Nov 2015 10:54:46 -0500 [thread overview]
Message-ID: <20151111155446.GA24431@cmpxchg.org> (raw)
In-Reply-To: <1447249697-13380-1-git-send-email-mhocko@kernel.org>
On Wed, Nov 11, 2015 at 02:48:17PM +0100, mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> __GFP_NOFAIL is a big hammer used to ensure that the allocation
> request can never fail. This is a strong requirement and as such
> it also deserves a special treatment when the system is OOM. The
> primary problem here is that the allocation request might have
> come with some locks held and the oom victim might be blocked
> on the same locks. This is basically an OOM deadlock situation.
>
> This patch tries to reduce the risk of such a deadlocks by giving
> __GFP_NOFAIL allocations a special treatment and let them dive into
> memory reserves after oom killer invocation. This should help them
> to make a progress and release resources they are holding. The OOM
> victim should compensate for the reserves consumption.
>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
>
> Hi,
> this has been posted previously as a part of larger GFP_NOFS related
> patch set (http://lkml.kernel.org/r/1438768284-30927-1-git-send-email-mhocko%40kernel.org)
> but Andrea was asking basically the same thing at LSF early this year
> (I cannot seem to find it in any public archive though). I think the
> patch makes some sense on its own.
I sent this right after LSF based on Andrea's suggestion:
https://lkml.org/lkml/2015/3/25/37
next prev parent reply other threads:[~2015-11-11 15:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 13:48 [PATCH] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves mhocko
2015-11-11 13:48 ` mhocko
2015-11-11 15:54 ` Johannes Weiner [this message]
2015-11-11 15:54 ` Johannes Weiner
2015-11-12 8:51 ` Michal Hocko
2015-11-12 8:51 ` Michal Hocko
2015-11-22 12:55 ` Vlastimil Babka
2015-11-22 12:55 ` Vlastimil Babka
2015-11-23 9:29 ` Michal Hocko
2015-11-23 9:29 ` Michal Hocko
2015-11-23 9:43 ` Vlastimil Babka
2015-11-23 9:43 ` Vlastimil Babka
2015-11-23 10:13 ` Michal Hocko
2015-11-23 10:13 ` Michal Hocko
2015-11-23 21:26 ` David Rientjes
2015-11-23 21:26 ` David Rientjes
2015-11-24 9:47 ` Michal Hocko
2015-11-24 9:47 ` Michal Hocko
2015-11-24 16:26 ` Johannes Weiner
2015-11-24 16:26 ` Johannes Weiner
2015-11-24 17:02 ` Michal Hocko
2015-11-24 17:02 ` Michal Hocko
2015-11-24 19:57 ` Johannes Weiner
2015-11-24 19:57 ` Johannes Weiner
2015-11-25 9:33 ` Michal Hocko
2015-11-25 9:33 ` Michal Hocko
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=20151111155446.GA24431@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.