From: Michal Hocko <mhocko@kernel.org>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: lsf-pc@lists.linux-foundation.org,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [LSF/MM ATTEND] memory allocation scope
Date: Thu, 15 Feb 2018 15:48:07 +0100 [thread overview]
Message-ID: <20180215144807.GH7275@dhcp22.suse.cz> (raw)
In-Reply-To: <8b9d4170-bc71-3338-6b46-22130f828adb@suse.de>
On Wed 14-02-18 16:51:53, Goldwyn Rodrigues wrote:
>
> Discussion with the memory folks towards scope based allocation
> I am working on converting some of the GFP_NOFS memory allocation calls
> to new scope API [1]. While other allocation types (noio, nofs,
> noreclaim) are covered. Are there plans for identifying scope of
> GFP_ATOMIC allocations? This should cover most (if not all) of the
> allocation scope.
There was no explicit request for that but I can see how some users
might want it. I would have to double check but maybe this would allow
vmalloc(GFP_ATOMIC). There were some users but most of them could have
been changed in some way so the motivation is not very large.
--
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>
next prev parent reply other threads:[~2018-02-15 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 22:51 Goldwyn Rodrigues
2018-02-15 3:53 ` NeilBrown
2018-02-15 14:19 ` Goldwyn Rodrigues
2018-02-15 14:48 ` Michal Hocko [this message]
2018-02-15 15:57 ` [Lsf-pc] " James Bottomley
2018-02-15 16:02 ` Michal Hocko
2018-02-15 16:06 ` 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=20180215144807.GH7275@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=rgoldwyn@suse.de \
/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