From: Michal Hocko <mhocko@suse.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCH 2/2] mm: introduce PF_MEMALLOC_NOWARN
Date: Sun, 28 Jan 2024 16:45:32 +0100 [thread overview]
Message-ID: <ZbZ2nDMkqawqDOEs@tiehlicka> (raw)
In-Reply-To: <20240126220756.395187-2-kent.overstreet@linux.dev>
On Fri 26-01-24 17:07:56, Kent Overstreet wrote:
> If we're using PF_MEMALLOC, we might have a fallback and might not to
> warn about a failing allocation - thus we need a PF_* equivalent of
> __GFP_NOWARN.
Could you be more specific about the user? Is this an allocation from
the reclaim path or an explicit PF_MEMALLOC one? It would be also really
helpful to explain why GFP_NOWARN cannot be used directly.
Thanks!
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-01-28 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 22:07 [PATCH 1/2] mm: introduce memalloc_flags_{save,restore} Kent Overstreet
2024-01-26 22:07 ` [PATCH 2/2] mm: introduce PF_MEMALLOC_NOWARN Kent Overstreet
2024-01-28 15:45 ` Michal Hocko [this message]
2024-01-28 19:43 ` Kent Overstreet
2024-01-29 10:48 ` Michal Hocko
2024-02-01 11:03 ` Kent Overstreet
2024-02-01 15:59 ` 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=ZbZ2nDMkqawqDOEs@tiehlicka \
--to=mhocko@suse.com \
--cc=djwong@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--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